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 363693 - gnome-pilot reproducable crash
gnome-pilot reproducable crash
Status: RESOLVED DUPLICATE of bug 136010
Product: gnome-pilot
Classification: Other
Component: conduit: backup
unspecified
Other other
: High critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-20 15:46 UTC by ronh
Modified: 2006-10-20 15:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description ronh 2006-10-20 15:45:45 UTC
From: Ron Heinsman <ronh@team.org.tw>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: gnome-pilot crash

Distribution: Ubuntu 6.06 (dapper)
Package: gnome-pilot
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: gnome-pilot crash
Bugzilla-Product: gnome-pilot
Bugzilla-Component: conduit: backup
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
During hotsync operations, gnome-pilot crashes. When I ran it in a 
terminal window, I could see that the specific item being backed up
was WiFiCoreLib. If the Pilot Applet is running, gnome-pilot crashes
as well with the backup conduit enabled.

Steps to reproduce the crash:
1. If the backup conduit is enabled, gnome-pilot crashes when it tries
to backup WiFiCoreLib.
2. 
3. 

Expected Results: Completed hotsync operation including files backup.


How often does this happen? Always with the backup conduit enabled.


Additional Information: Using a Palm TX. Last few lines before the crash
were:
backupconduit-Message: PPtools not modified since last sync
backupconduit-Message: Font Silo Library not modified since last sync
backupconduit-Message: wifidbLib-WMru not modified since last sync
backupconduit-Message: wifibusiflib not modified since last sync
backupconduit-Message: Making backup of WiFiCoreLib




Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224504672 (LWP 15191)]
[New Thread -1242895440 (LWP 15275)]
[New Thread -1234502736 (LWP 15265)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224504672 (LWP 15191))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libpisock.so.8
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 dlp_ReadResourceByIndex
    from /usr/lib/libpisock.so.8
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-10-20 15:46 -------

Comment 1 Matt Davey 2006-10-20 15:52:58 UTC
Hi,
This is a known issue with certain palm databases and pilot-link versions prior
to 0.12.x.  See this master bug, which contains a workaround for gnome-pilot in
comment 9:

http://bugzilla.gnome.org/show_bug.cgi?id=136010

The good news is that updated gnome-pilot and pilot-link packages are available
for Ubuntu, courtesy of Daniel Holbach.  If they're not available for you with
a plain update, take a look at:

https://wiki.ubuntu.com/PDATesters

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