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 316012 - gpliotd crashed when syncing
gpliotd crashed when syncing
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: 2005-09-11 17:53 UTC by xdrudis
Modified: 2006-03-13 22:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description xdrudis 2005-09-11 17:53:59 UTC
Distribution: Debian testing/unstable
Package: gnome-pilot
Severity: normal
Version: GNOME2.10.2 unspecified
Gnome-Distributor: Debian
Synopsis: gpliotd crashed when syncing
Bugzilla-Product: gnome-pilot
Bugzilla-Component: gpilotd
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.1)
Description:
Description of the crash:
I had to restart the daemon and replug my Palm Tungsten e2. The pressing
sync on the Palm
caused a dialog to appear and show progress syncing, until the gnome
crash dialog appeared,
when the gpilot dialog said EToDo was finalized syncing and the palm
said "Web" was syncing...

Steps to reproduce the crash:
1. Restart gpilotd
2. Unplug and replug the USB cable to the palm
3. Press sync on the palm and wait.

Expected Results:
Syncing complete

How often does this happen?
Last time I blamed it on the fact that I had just moved the mouse
(wireless
mouse, with the base plugged to another USB port). This time I hadn't
touched
the mouse. So it seems to happen always.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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 -1222875456 (LWP 5345)]
[New Thread -1241588816 (LWP 5494)]
[New Thread -1233200208 (LWP 5490)]
(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)
(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)
0xb7555201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libpisock.so.8
  • #10 ??
  • #11 ??
    from /usr/lib/libpisock.so.8
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 dlp_ReadResourceByIndex
    from /usr/lib/libpisock.so.8




------- Bug moved to this database by unknown@gnome.bugs 2005-09-11 17:53 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was xdrudis@tinet.org.

Comment 1 Sebastien Bacher 2005-11-20 16:51:13 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Can you get us one with debugging symbols?
Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Matt Davey 2006-03-13 22:57:15 UTC

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