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 372945 - Crash when synchronising "J9 MIDP Bundle"
Crash when synchronising "J9 MIDP Bundle"
Status: RESOLVED DUPLICATE of bug 136010
Product: gnome-pilot
Classification: Other
Component: gpilotd
unspecified
Other other
: High critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-09 13:27 UTC by mark
Modified: 2006-11-09 20:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description mark 2006-11-09 13:26:14 UTC
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Crash when synchronising "J9 MIDP Bundle"

Distribution: Ubuntu 6.06 (dapper)
Package: gnome-pilot
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crash when synchronising "J9 MIDP Bundle"
Bugzilla-Product: gnome-pilot
Bugzilla-Component: gpilotd
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
After installing IBM's JVM on my Treo 600 and the opera mini browser,
gpilotd will always crash when it gets to synchrnoising J9 MIDP Bundle

Steps to reproduce the crash:
1. Install IBM's JVM on the palm (specifically treo 600)
2. Synchronise to backup the database and the gpilotd process will
crash
3. 

Expected Results:
Gpilotd should synchronise properly and not crash.

How often does this happen?
Repeatable each time I sync.

Additional Information:
Opera mini also installed at the same time, may be linked but doesn't
look like it from the outset.


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 -1224856928 (LWP 28177)]
[New Thread -1242981456 (LWP 688)]
[New Thread -1234588752 (LWP 681)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224856928 (LWP 28177))

  • #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-11-09 13:27 -------

Comment 1 André Klapper 2006-11-09 20:43:10 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 is fixed by upgrading to pilot-link 0.12.0. gnome-pilot 2.0.14 will support pilot-link 0.12.0.

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