Bug 327774 – Crash on pilot 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 327774 - Crash on pilot sync


Summary:	Crash on pilot 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-19 23:28 UTC by troy
Modified:	2006-01-28 23:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description troy 2006-01-19 23:28:51 UTC

Distribution: Fedora Core release 4 (Stentz)
Package: gnome-pilot
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Crash on pilot sync
Bugzilla-Product: gnome-pilot
Bugzilla-Component: gpilotd
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


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 -1208629568 (LWP 21930)]
(no debugging symbols found)
0x00706402 in __kernel_vsyscall ()

+ Trace 65385

Thread 1 (Thread -1208629568 (LWP 21930))

#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-19 23:28 -------

Comment 1 Matt Davey 2006-01-20 15:36:27 UTC

What version of pilot-link are you using?  Is there an update you can apply?

Comment 2 troy 2006-01-20 15:45:28 UTC

The version I a using is pilot-link-0.12.0-0.pre4.0.fc4.2.

The crasing seems to have stopped after I upgraded gnome-pilot to gnome-pilot-2.0.13-5.netsyncpatch.

Comment 3 Matt Davey 2006-01-20 16:50:25 UTC

That's great!

Thanks for the feedback on the netsyncpatch.  I presume
you also upgraded the pilot-link and gnome-pilot-conduit packages?

Comment 4 troy 2006-01-20 18:11:54 UTC

I did, but I lost the evolution conduits. I am running a newer version of evolution than what you link to. I am probably going to use rpm2cpio to pull them out the evolution package you link to.

Comment 5 Matt Davey 2006-01-21 12:12:41 UTC

Do you need the later version of evolution?  You could recompile from the SRPMS that are also available from the same site.

Comment 6 Karsten Bräckelmann 2006-01-28 23:38:57 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 ***