Your message dated Thu, 24 Feb 2005 11:05:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#290177: hot sync doesn't work when jpilot launched from
Debian menu
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 12 Jan 2005 23:23:14 +0000
>From [EMAIL PROTECTED] Wed Jan 12 15:23:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail1.mesanetworks.net [70.85.18.196]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1Corpa-0000W1-00; Wed, 12 Jan 2005 15:23:14 -0800
Received: (qmail 7257 invoked from network); 12 Jan 2005 22:12:37 -0000
Received: from admin.mesanetworks.net (69.93.53.226)
by mail1.mesanetworks.net with SMTP; 12 Jan 2005 22:12:37 -0000
Received: from [66.54.160.120] (helo=big.lan.gnu)
by admin.mesanetworks.net with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.43)
id 1CoqtT-00006Q-K4; Wed, 12 Jan 2005 15:23:11 -0700
Received: from pecondon by big.lan.gnu with local (Exim 4.34)
id 1CoqrL-0008Bw-1d; Wed, 12 Jan 2005 15:20:59 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Paul E Condon <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: hot sync doesn't work when jpilot launched from Debian menu
X-Mailer: reportbug 3.2
Date: Wed, 12 Jan 2005 15:20:58 -0700
Message-Id: <[EMAIL PROTECTED]>
X-MesaNetworks-MailScanner-Information: Please contact the ISP for more
information
X-MesaNetworks-MailScanner: Found to be clean
X-MailScanner-From: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: jpilot
Version: 0.99.7-0.99.8-pre6-1
Severity: normal
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (600, 'testing'), (60, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages jpilot depends on:
ii debconf 1.4.34 Debian configuration management sy
ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libglib2.0-0 2.4.8-1 The GLib library of C routines
ii libgtk2.0-0 2.4.14-2 The GTK+ graphical user interface
ii libpango1.0-0 1.6.0-3 Layout and rendering of internatio
ii libpisock8 0.11.8-10 Library for communicating with a P
-- debconf information:
* shared/pilot/port: ttyUSB0
hot sync does work when I launch jpilot for a command line in gnome terminal
but not when I launch using the Debian menu in the GUI
By 'not work' I mean that after a long pause, visor reports that it is
unable to connect to the computer, and, of course, there is no exchange of info
I guess it is an incorrectly configured entry in the menu. but I lack the
skills to check it out. GUI is magic to me.
Also I think visor is actually on USB1, but BTS reports as above.
---------------------------------------
Received: (at 290177-done) by bugs.debian.org; 24 Feb 2005 10:08:16 +0000
>From [EMAIL PROTECTED] Thu Feb 24 02:08:16 2005
Return-path: <[EMAIL PROTECTED]>
Received: from rousseau.net1.nerim.net (vectra.maison.bogus) [80.65.224.14]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D4Fuq-0003T9-00; Thu, 24 Feb 2005 02:08:16 -0800
Received: from acer.maison.bogus ([192.168.0.168])
by vectra.maison.bogus with esmtp (Exim 3.35 #1 (Debian))
id 1D4Fs2-0000CU-00; Thu, 24 Feb 2005 11:05:22 +0100
Received: from rousseau by acer.maison.bogus with local (Exim 4.34)
id 1D4Frq-0001oV-N4; Thu, 24 Feb 2005 11:05:10 +0100
Date: Thu, 24 Feb 2005 11:05:10 +0100
From: Ludovic Rousseau <[EMAIL PROTECTED]>
To: Paul E Condon <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#290177: hot sync doesn't work when jpilot launched from Debian
menu
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Le Friday 14 January 2005 � 09:46:41, Paul E Condon a �crit:
> On Fri, Jan 14, 2005 at 04:27:22PM +0100, Ludovic Rousseau wrote:
> > Le Wednesday 12 January 2005 ? 15:20:58, Paul E Condon a ?crit:
> > > -- debconf information:
> ...snip...
> >
> > I don't know how the USB port is attributed. If you think it is USB1 you
> > can change the jpilot configuration. It is in
> > File->Preferences->Settings, change the serial port from /dev/pilot to
> > /dev/ttyUSB1.
>
> I set up my system according to some instructions that came in the package.
> These instructions suggested adding a line to my .bashrc:
>
> export PILOTPORT=/dev/ttyUSB1
>
> This works for command line invocation of jpilot, but not, of course, for
> menu invocation. I changed the soft link per your suggestion and the
> problem is resolved.
The problem is that your ~/.bashrc file is _not_ evaluated if you start
jpilot from the menu. So PILOTPORT is then not defined.
What you should de is follow instructions in
/usr/share/doc/jpilot/README.gz
"SERIAL PORT SETUP:
When syncing, jpilot uses the port and speed settings out of the
preferences menu. If the port is blank then jpilot will use the
PILOTPORT environment variables, as does pilot-link. If these are
blank then jpilot will default to /dev/pilot."
The preferred method is to set the port jpilot preferences. The use of
PILOTPORT is abandonned in the new pilot-link package so you should
change your configuration now.
> Perhaps a small change in the documentation is called for.
I agree. Where exactly did you find the information about PILOTPORT?
Bye,
--
Dr. Ludovic Rousseau [EMAIL PROTECTED]
-- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
