Comment 6 for bug 21689

(In reply to comment #5)
> (In reply to comment #4)
>
> > I tried to open gpilotd in a terminal but I don't
> > know how to get a GUI (sorry, I'm a noob).
>
> run "gpilotd" from a command line so you can get the debug output here and note
> what it says. Then use evolution as usual and copy between the window with the
> log to bugzilla
>
> Hi, sorry I haven't replied but I had to reinstall Breezy due to a few bugs.
Now, however, I can't get gnome-pilot to recognize my Tungsten at all. I've
followed the same procedure I used in Hoary and also in Breezy, but something's
awry. I've asked a couple other forum members who posted the same problem to
look at this bug and send you guys the error messages in the meantime. I'll get
back to you if I can get it working again. One thing I should mention is that
the name of the device in the udev rules (ubuntu guide) is not 'Palm Handheld'
for the Palm Tungsten T5, it's 'palmOne'.
> > I also don't know how to make a gdb
> > trace? If you would send me some how-to I'll try it out. I won't be back at my
> > computer until late tomorrow as I'll be working away from it until then.
>
> if it crashes:
> - gdb gpilotd
> (gdb) run
> ... crash
> (gdb) thread apply all bt
>
>
> Let me know if you need other precisions on this