Bug 358069 – gnome-pilot crashes at Making Backup of Bluetooth Device Cache

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 358069 - gnome-pilot crashes at Making Backup of Bluetooth Device Cache


Summary:	gnome-pilot crashes at Making Backup of Bluetooth Device Cache


Status:	RESOLVED DUPLICATE of bug 136010

Product:	gnome-pilot
Classification:	Other
Component:	conduit: backup
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-09-28 01:26 UTC by Rowland Cheshire
Modified:	2006-09-28 11:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Rowland Cheshire 2006-09-28 01:26:06 UTC

Distribution: Slackware Slackware 10.2.0
Package: gnome-pilot
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Dropline GNOME
Synopsis: gnome-pilot crashes at Making Backup of Bluetooth Device Cache
Bugzilla-Product: gnome-pilot
Bugzilla-Component: conduit: backup
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
During Network HotSync gnome-pilot crashes.  

Steps to reproduce the crash:
1. Setup Network Sync using dund.
2. Enable Backup conduit
3. Hotsync

Expected Results:


How often does this happen?
Always

Additional Information:
Tungsten E2.
Subsequent tries crash almost immediately at the first backup i.e
DocsToGo.



Debugging Information:

Backtrace was generated from '/usr/libexec/gnome-pilot'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225288000 (LWP 8790)]
[New Thread -1242342480 (LWP 12267)]
[Thread debugging using libthread_db enabled]
[New Thread -1225288000 (LWP 8790)]
[New Thread -1242342480 (LWP 12267)]
[Thread debugging using libthread_db enabled]
[New Thread -1225288000 (LWP 8790)]
[New Thread -1242342480 (LWP 12267)]
[New Thread -1233953872 (LWP 12263)]
0xb73e5411 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 73436

Thread 3 (Thread -1233953872 (LWP 12263))

#0 poll
from /lib/tls/libc.so.6
#1 g_main_loop_get_context
from /usr/lib/libglib-2.0.so.0
#2 ??
#3 ??
#4 ??
#5 ??
from /usr/lib/libglib-2.0.so.0
#6 ??
#7 ??
#8 ??
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 ??
#22 ??
from /usr/lib/libglib-2.0.so.0
#23 ??
#24 ??
from /usr/lib/libebook-1.2.so.5
#25 ??
#26 ??
#27 ??
#28 e_book_get_addressbooks
from /usr/lib/libebook-1.2.so.5
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0





------- Bug created by bug-buddy at 2006-09-28 01:26 -------

Comment 1 Karsten Bräckelmann 2006-09-28 01:41:02 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.

Can you reproduce the crash, Rowland?

Comment 2 Matt Davey 2006-09-28 11:28:02 UTC

This looks like a duplicate of #136010:
http://bugzilla.gnome.org/show_bug.cgi?id=136010

See comment 9 in bug 136010 for details of a workaround (you need to
find the name of the database being backed up, and list it in the
exclude_files list).

This bug is in pilot-link 0.11.*, and is fixed in 0.12.x

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