This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
anuary 16, 2010 1:34:21 PM GMT -05:00 US/Canada Eastern
Subject: [Bug 125056] Re: gpilotd crashed with SIGSEGV in free_Memo()
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
** Changed in
** Description changed:
Binary package hint: gnome-pilot
First sync crash, second good, third crash, and so on...
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Jul 10 10:11:46 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gpilotd
NonfreeKernelMo
** Changed in: gnome-pilot (Ubuntu)
Importance: Undecided => Medium
--
gpilotd crashed with SIGSEGV in free_Memo()
https://bugs.launchpad.net/bugs/125056
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
Did not get the apport stack trace, but in running gpilotd on the command
line it would appear that I am tripping over this bug:
etodoconduit-Message: set_pilot_id: setting to 4214792
etodoconduit-Message: free_match: freeing
etodoconduit-Message: post_sync: ToDo Conduit v.0.1.6
etodoconduit-Mes
** Visibility changed to: Public
--
gpilotd crashed with SIGSEGV in free_Memo()
https://bugs.launchpad.net/bugs/125056
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
