GNOME Bugzilla – Bug 146595
Gpilotd crashes on second hotsync (probably UTF-8 related)
Last modified: 2013-09-13 12:33:03 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 second hotsync Bugzilla-Product: gnome-pilot Bugzilla-Component: gpilotd Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: I got the crash notification window. Steps to reproduce the crash: 1. Start pilot applet 2. plug in Palm (mine is Tungsten E USB) 3. do a hot-sync 4. do another hot-sync Expected Results: Minimal sync (mostly, time) How often does this happen? Every time. Additional Information: ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 03:29 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-pilot". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was sedrez@sedrez.ods.org. 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.
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.
See bug report #147412 for backtrace. http://bugzilla.gnome.org/show_bug.cgi?id=147412
*** Bug 147406 has been marked as a duplicate of this bug. ***
*** Bug 147412 has been marked as a duplicate of this bug. ***
Reopening since a stack trace is now available...
The stack trace provided looks like it may match the one in bug 136010; this may be a duplicate of that one.
*** Bug 149012 has been marked as a duplicate of this bug. ***
Bug 149012 provided the extra information of a warning that appeared at the time of the crash: (process:4269): GLib-CRITICAL (recursed) **: file gstring.c: line 672 (g_string_erase): assertion `pos >= 0' failed aborting... The reporter of that bug also stated that they had a lot of French entries in the addressbook; that may or may not be helpful but I thought I'd mention it.
The bug I've logged (#149012) seems to be a duplicate of this one, therefore I am adding comments here. I remove all special characters from my entries in the pilot (all frecn accentued chars) and tried the synchro again --> it worked !! I definitively suspect something related to the handling of UTF-8 chars
Cool, thanks for the info. I'm updating the summary.
*** Bug 149615 has been marked as a duplicate of this bug. ***
reassigning to evolution conduits.
this bug report is nearly two years old, is this still valid? could anyone please update this? thanks in advance.