After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 345146 - gnome-pilot crashes when doing hotsync
gnome-pilot crashes when doing hotsync
Status: RESOLVED DUPLICATE of bug 136010
Product: gnome-pilot
Classification: Other
Component: gpilotd
unspecified
Other other
: High critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-17 00:01 UTC by naqvik
Modified: 2006-06-17 00:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description naqvik 2006-06-17 00:01:20 UTC
Distribution: Ubuntu 5.10 (breezy)
Package: gnome-pilot
Severity: Normal
Version: GNOME2.12.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: gnome-pilot crashes when doing hotsync
Bugzilla-Product: gnome-pilot
Bugzilla-Component: gpilotd
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:


Steps to reproduce the crash:
A: initial configuration
1. Under the System-Preferences menu, choose PalmOS devices.
2. Successfully configure a PalmTX device
3. Under the Conduits tab, all conduits are initially disabled.  Enable
just the Backup Conduit.  Use the default settings.
4. Under the Devices tab, the display shows name=Cradle,
port=/dev/pilot
speed=57600, Type=USB
5. Under the Pilots tab, the display shows name=MyPilot, ID=22514,
UserName=naqvik
6. I believe the device is correctly configured.

B: using gnome-pilot to backup the palmTX
1. Plug in Palm TX into USB port on desktop machine running ubuntu
breezy.
2. press the hotsync button
3. The palmTX display shows that the user is being identified.
4. The palmTX display shows various files being synchronized.
5. Listing the ~/MyPilot directory shows over 100 files have been
transferred.
6. An Error dialog box pops up:
  The Application "gpilotd" has quit unexpectedly.

Expected Results:
The files should be all synchronized and the application should
successfully terminate.


How often does this happen?
Every time.  It has never worked successfully.

Additional Information:
I'm using ubuntu breezy.  The log on the PalmTX shows several files were
backed up.  The following packages seem to be relevant
gnome-pilot 2.0.13-0ubuntu10
gnome-pilot-conduits 2.0.13-0ubuntu2
libgnome-pilot2 2.0.13-0ubuntu10

Debugging Information:

Backtrace was generated from '/usr/bin/gpilotd'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)

[...many identical lines removed...]

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224653120 (LWP 11685)]
[...more identical lines removed...]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libpisock.so.8
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 dlp_ReadResourceByIndex
    from /usr/lib/libpisock.so.8




------- Bug created by bug-buddy at 2006-06-17 00:01 -------

Comment 1 Elijah Newren 2006-06-17 00:54:30 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

Matches the stack trace in bug 336371; comments from that bug:
  For a workaround, take a look at comment 9 in bug #136010

*** This bug has been marked as a duplicate of 136010 ***