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 362799 - Crash during HotSync operation on a Palm Tungsten E
Crash during HotSync operation on a Palm Tungsten E
Status: RESOLVED DUPLICATE of bug 136010
Product: gnome-pilot
Classification: Other
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-17 07:56 UTC by batosai
Modified: 2006-10-17 08:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description batosai 2006-10-17 07:55:16 UTC 
Distribution: Ubuntu 6.06 (dapper)
Package: gnome-pilot
Severity: blocker
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crash during HotSync operation on a Palm Tungsten E
Bugzilla-Product: gnome-pilot
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
During the Hotsync operation, most of the databases are saved and then,
the progress window crashes during the backup of the photos.

Steps to reproduce the crash:
1. Plug the Handheld with the USB cable
2. Perform a HotSync operation

Expected Results:
Full backup of the databases.

How often does this happen?
Always.

Additional Information:
The handheld is correctly configured and recognized by the system.
The only activated conduit is the 'backup' one : at the moment of the
activation, I get an error message saying "Unable to instantiate Backup
conduit.", but it seems to work anyway.
After a crash, the handheld is no longer able to connect the the
desktop...


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 -1224627552 (LWP 5547)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76747

Thread 1 (Thread -1224627552 (LWP 5547))

  • #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-17 07:56 -------
Comment 1 Matt Davey 2006-10-17 08:10:24 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 ***