Bug 146780 – gpilotd crashes on hotsync

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 146780 - gpilotd crashes on hotsync


Summary:	gpilotd crashes on hotsync


Status:	RESOLVED DUPLICATE of bug 147412

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

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gnome-pilot Maintainers
QA Contact:	gnome-pilot Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-06-22 00:35 UTC by Paulo Sedrez
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.5/2.6

Attachments
Stack trace of gpilotd (5.92 KB, text/plain) 2004-07-12 13:34 UTC, Paulo Sedrez	Details

Description Paulo Sedrez 2004-07-09 10:36:47 UTC

Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-pilot
Severity: major
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: gpilotd crashes on hotsync
Bugzilla-Product: gnome-pilot
Bugzilla-Component: gpilotd
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:

The gpilotd daemon crashes when there is no file to upload. The
gnome-pilot-applet informs gpilotd died, but says nothing more.

Steps to reproduce the crash:
1. send a file for later
    gpilot-install-file --later xxx.pdb
2. plug the pilot in (mine is Tungsten E - USB)
3. hotsync (goes OK)
4. unplug the pilot, then plug it again
5. hotsync (gpilotd dies)

Expected Results:

Minimal roundup update, terminates normally

How often does this happen?

Every time.

Additional Information:

Fedora Core 2, latest updates except kernel (2.6.5-1.358, did not reboot
since last update); Duren 1800+ (1260MHz), 512MB Ram, HD 80GB; some
updates from freshrpms (mplayer & related).




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 06:36 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-pilot".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Elijah Newren 2004-07-09 20:57:30 UTC

Thanks for the bug report. Without a stack trace from the crash it's very hard
to determine what caused the crash.  Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information about getting
a useful stack trace.

Comment 2 Paulo Sedrez 2004-07-12 13:34:59 UTC

Created attachment 29465 [details]
Stack trace of gpilotd

Backtrace from bugbuddy for gpilotd.

Comment 3 Paulo Sedrez 2004-07-12 13:35:40 UTC

Trace herein supplied:

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -150322528 (LWP 24265)]
0x0050f402 in ?? ()

+ Trace 48513

Thread 1 (Thread -150322528 (LWP 24265))

#0 ??
#1 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 raise
from /lib/tls/libc.so.6
#6 abort
from /lib/tls/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_string_erase
from /usr/lib/libglib-2.0.so.0
#10 _g_log_fallback_handler
from /usr/lib/libglib-2.0.so.0
#11 g_log_default_handler
from /usr/lib/libglib-2.0.so.0
#12 g_logv
from /usr/lib/libglib-2.0.so.0
#13 g_log
from /usr/lib/libglib-2.0.so.0
#14 gnome_real_pilot_conduit_backup_backup
at backup_conduit.c line 422
#15 ___marshal_Sig1
at gnome-pilot-conduit-backup.c line 88
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emitv
from /usr/lib/libgobject-2.0.so.0
#19 gnome_pilot_conduit_backup_backup
at gnome-pilot-conduit-backup.c line 391
#20 backup_foreach
at manager.c line 271
#0 ??

Comment 4 Elijah Newren 2004-07-12 15:30:57 UTC

Thanks for following up.  This matches the other stack trace you provided; I'm
reopening so I can mark as a duplicate.

Comment 5 Elijah Newren 2004-07-12 15:31:21 UTC


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