Distribution: Debian testing/unstable
Package: gnome-pilot
Severity: critical
Version: GNOME2.8.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: The Application "gpilot-applet" has quit unexpectedly. You can inform the developers of what happened to help them fix it.  Or you can restart the application right now.
Bugzilla-Product: gnome-pilot
Bugzilla-Component: applet
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:

from clicking on icon on top panel, immediately get error dialog as in
summary above.  previously able to enter connection settings, then
synchronise from handspring visor cradle on ttyUSB1, into evolution
2.02. ubuntu 4.1 just installed and updated using apt-get.  prior to
update unable to synchronise. 

Steps to reproduce the crash:

1. as above
2. 
3. 

Expected Results:

gpilot dialog window to check settings etc

How often does this happen?

repeatedly

Additional Information:

from clicking on gnome-pilot icon on top panel, i immediately get error
dialog as in summary above.  previously able to enter connection
settings, then synchronise from handspring visor cradle on ttyUSB1, into
evolution 2.02. ubuntu 4.1 just installed and updated using apt-get. 
prior to update unable to synchronise.  tried running shell script for
visor setup as in www.sourceforge.net --> automagic --> visor, which did
not work so i plowed through the manual procedure set out in the "hint"
quoted below, but which was designed for jpilot and requires coldsync. 
see below text from two Hints from Linspire.com support.  this is also a
debian based distro but optimised for KDE:

======================================
Hint 139 - How to Hotsynch a Handspring Visor

Using a Handspring Visor on USB Cradle in Lindows with Coldsynch& Jpilot


I am posting a set of procedures used to setup my Handspring Visor in
Lindows. 

The underlying assumption is that you have a computer with USB port, 
Lindows 2+, a Handspring Visor with the Palm OS & USB cradle available 

for use. The USB cradle is plugged into the computer at a USB port & the

Handspring Visor is on the cradle. 

Please note that the shell commands below do not 
include the A. or B. etc. 

Caveats & applicable use... 

Please note that you cannot hotsync email under this configuration. 
Furthermore, jpilot is designed to run in a home directory. It cannot be

easily changed to store files on a network that will be accessable by 
other parties that have access to the calander. This solution is also 
not ideal in a dual boot situation, as jpilot & coldsynch are not 
windows compatable. Compatability is an issue in an office where a 
number of people keep track of the company calander, and would not want 

to have to wait for the machine to reboot to check the calander for 
available appointment times. 

Steps taken to set up a Handspring Visor on USB Cradle in Lindows with
Coldsynch & Jpilot: 

1. Click and Run Jpilot 
2. Click and Run Coldsynch 
3. Click and Run Emacs 
4. Go to the shell and type: 
A. cd /dev 
B. ln -s /dev/ttyUSB1 pilot 
C. ln -s /dev/ttyUSB1 palm 
D. modprobe visor 
E. modprobe usb-uhci 
F. modprobe usb-ohci 
G. mknod /dev/ttyUSB0 c 188 0 
H. mknod /dev/ttyUSB1 c 188 1 
I. chmod 666 /dev/ttyUSB* 
(Note on steps E & F. One of the commands will work, one will give you
an error. Just ignore it.) 
G. emacs /etc/fstab 
5. Once Emacs opens /etc/fstab: 
A. go to the bottom of the file. 
B. Note that the last line has the cursor on it at the left, but it is
blank. 
C. Hit return to add another blank line. 
D. On the line you just created type the following: 
none /proc/bus/usbdevfs defaults 0 0 
6. Reboot 
7. Go to shell and type: 
A. mkdir visorbackup 
B. coldsync -p /dev/ttyUSB1 -mb visorbackup 
C. cd visorbackup 
D. ls -l 
8. Note the presence of sundry files in the visorbackup directory. You 

are now ready to use jpilot. 
9. Go to the shell and type: 
A. jpilot 
10. Once jpilot opens up, go to file/preferences and click on the 
settings tab. 
11. Change the serial port setting to read: /dev/ttyUSB1 
12. Take note of the 4 black boxes on the left 
13. Click on the top black box 
14. Click on the New Record button at the right 
15. Type "Testing" inside the upper of the two white boxes below the new

record button 
16. Click on the Add Record button to save your setting 
17. Press the Hotsynch button to enter the Kernel memory. You must do
this before Hotsyncing. 
18. Click on the small sync button at the left. It is located below the
four black boxes described earlier 
19. When the white box displays a message asking you to press the
hotsynch button, press the hotsynch button to start the hotsynch
process. 
20. Note that the hotsynch process starts after a short delay. You will
hear a few beeps. 
21. When the Handspring Visor displays the message "Hotsync Operation
Complete" check your Handspring's calander for the testing entry. 
22. If you note that the testing entry is present in the visor, you are
finished. 

James Leone
Edited by kevin@lindows.com (10/20/02 04:58 PM)

--------------------------version 2
10-11-2002---------------------------------

Hint 139 V2 - How to Hotsynch a Handspring Visor

Using a Handspring Visor on USB Cradle in Lindows with Coldsynch &
Jpilot

I just finished making and testing a script that will automatically set
up your handspring visor by typing "sh visorsetup.sh" at the console.
Released under the GPL. Palm Pilot Users: This should work for you too,
give it a test and feedback to verify.

Tested and verified to work in Lindows 2.3.4, but should work in other
versions. 

It is available for download at: 

http://www.morton2001.org/visorsetup.sh

After you download the file, go to Programs, Utilities and then console.
Once in the console, type sh visorsetup.sh, and answer Y to the
questions, and provide the info it requests, etc. 

---------------------------------------------------------------------------------

If you get "Warning: no device on /usb/ttyUSB1. sleeping", you have to
ctrl-C when it says it's sleeping. Then all you have to do is start
jpilot. If that does not work then just run the script again and answer
'no' to the apt-get for the first time question.

Ensure that you when you have started J-Pilot you go to
Preferences/Settings and manually add /dev/ttyUSB1 to get it to sync.

---------------------------------------------------------------------------------

If after a reboot it does not work, and gives the following message:

pi_bind invalid arguement 
Check your serial port and settings 
exiting with status -10 

- try a slower speed and then reboot

---------------------------------------------------------------------------------

If after a reboot it does not work, and gives the following message:

Error: Can't look up my address. 
gethostbyname: No such file or directory 
Error: Can't get host ID. 
total 0 
If there are files in this directory than your Visor has been configured

If not, try to use it once jpilot starts 
usage: more [-dflpcsu] [+linenum | +/pattern] name1 name2 ... 

Remember that you actually have to press the sync button before
answering that question. Even if all it does is tell you that it can't
connect. Go ahead and try jpilot anyway. First try typing 'jpilot' at
the console. When it opens try to sync (jpilot first - Visor second). If
that doesn't work, close the console and open jpilot from the program
menu. 

Go ahead and try jpilot anyway. First try typing 'jpilot' at the
console. When it opens try to sync (jpilot first - Visor second). If
that doesn't work, close the console and open jpilot from the program
menu. 

------------------------Update
27-12-2002------------------------------------------------
 
The Visor setup script has moved to Sourceforge.net ---> Automagic.

---------------------------------------------------------------------------------

Palm Pilot  

I haven't had much sucess with Palm Pilots, although the procedure AFAIK
is the same as with the Handspring Visor, as they both are supposed to
use the same Linux device driver. It reportedly has worked for various
models of Palm Pilots. 

Now with that said, I know as far as the Handspring Visor is concerned,
the Hotsync button must be pressed once for the kernel to detect that it
is present, and then click on the jpilot sync button, and finally press
the hotsync button again. 

I am also getting the general impression from other forums and lists
that I am on, that the Device File System (devfs) is a little buggy. The
newer versions of most distributions have only recently started using
devfs, and another system had been used for a long time until recently
AFAIK. 

So, the device could be properly setup and still not work.

James Leone 
======================================


Debugging Information:

Backtrace was generated from '/usr/bin/gpilot-applet'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/i686/cmov/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)...(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)...[Thread debugging using
libthread_db enabled]
[New Thread 1088867072 (LWP 5522)]
(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)...0xffffe410 in __kernel_vsyscall
()

+ Trace 55372

------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-06 10:44 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-pilot".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was larry.hall@ntlworld.com.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.