Package: jpilot
Version: 0.99.7-0.99.8-pre6-1
Followup-For: Bug #287940

I'm seeing similar problems since upgrading to kernel 2.4.27-6
yesterday.  I didn't see problems with kernel 2.4.27-4 (I think:
anyway a previous 2.4.27 kernel-image package).

Running pilot-xfer -l appears to accurately list the pilot's
databases.

Running jpilot -d doesn't show anything that appears interesting or
out of the ordinary.

Initially I had configured jpilot to use /dev/ttyS0.  I tried
symlinking from /dev/pilot, but no change.

"cat < /dev/pilot" and "cat < /dev/ttyS0" both seem to work fine.
That is, they show a bunch of garbage when I hit the hotsync button.

This may be a kernel bug, but I'm not sure how to report it
meaningfully to the kernel maintainers.

Using pilot-xfer -s /home/jeff/.jpilot/ seems to work, although I
killed it after several minutes, since I'm not completely clear on the
difference between -u, -s, etc.  (My pilot databases were unchanged.)

The jpilot issue remains even at 9600 baud.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages jpilot depends on:
ii  debconf                     1.4.30.11    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: None


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to