Bug 149111 – Crash on backup - getting worst!

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 149111 - Crash on backup - getting worst!


Summary:	Crash on backup - getting worst!


Status:	RESOLVED DUPLICATE of bug 147412

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-08-03 01:10 UTC by Paulo Sedrez
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Paulo Sedrez 2004-08-03 01:12:49 UTC

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

Crashs during backup. No particular case, just crash. I have reported two similar bugs, that crashed only on certain conditions, but now I can't get the backup done in any case.

Steps to reproduce the crash:
1. Start applet (starts daemon)
2. Hotsync

Expected Results:
The backup.

How often does this happen?
Every time.

Additional Information:
Fedora 2 with updates, including freshrpms & dag, but NOT the components
involved.

$ rpm -q kernel gnome-pilot pilot-link libusb glibc
kernel-2.6.6-1.435.2.3
gnome-pilot-2.0.10-6.1
pilot-link-0.11.8-3.1
libusb-0.1.8-2.1
glibc-2.3.3-27

$ uname -a
Linux sedrez.ods.org 2.6.6-1.435.2.3 #1 Thu Jul 1 08:25:29 EDT 2004 i686
athlon i386 GNU/Linux



Debugging Information:

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

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

+ Trace 49050

Thread 1 (Thread -150517920 (LWP 28661))

#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 ??





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-02 21:12 -------


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 Vidar Hauge 2004-11-06 20:40:08 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 147412 ***