Bug 328467 – crashes when attempting to sync

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 328467 - crashes when attempting to sync


Summary:	crashes when attempting to sync


Status:	RESOLVED DUPLICATE of bug 274032

Product:	gnome-pilot
Classification:	Other
Component:	gpilotd
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-pilot Maintainers
QA Contact:	gnome-pilot Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-01-24 18:55 UTC by bfield
Modified:	2006-01-28 23:39 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description bfield 2006-01-24 18:55:54 UTC

Distribution: Unknown
Package: gnome-pilot
Severity: Normal
Version: GNOME2.12.1 unspecified
Gnome-Distributor: www.nrpms.net
Synopsis: crashes when attempting to sync
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:
1. connect tungsten t3
2. press hot-sync button
3. crash

Expected Results: sync with evolution 2.4


How often does this happen?
every attempt

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209002304 (LWP 4862)]
(no debugging symbols found)
0x00276402 in __kernel_vsyscall ()

+ Trace 65564

Thread 1 (Thread -1209002304 (LWP 4862))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 pi_listen
from /usr/lib/libpisock.so.9
#5 device_equal_by_io
#6 network_device_err
#7 g_main_context_wakeup
from /usr/lib/libglib-2.0.so.0
#8 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#11 main





------- Bug created by bug-buddy at 2006-01-24 18:55 -------

Comment 1 Matt Davey 2006-01-26 09:56:27 UTC

This looks like a duplicate of:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175859
and
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158809

The latter link contains a workaround which might help.

Comment 2 Karsten Bräckelmann 2006-01-28 23:39:03 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.


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