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 67860 - pilot setup crashed
pilot setup crashed
Status: RESOLVED DUPLICATE of bug 64885
Product: gnome-pilot
Classification: Other
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-01-02 15:57 UTC by kern
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kern 2002-01-02 15:58:39 UTC 
Package: gnome-pilot
Severity: normal
Version: 0.1.63
Synopsis: pilot setup crashed
Bugzilla-Product: gnome-pilot
Bugzilla-Component: general

Description:
I had switched my pilot to use /dev/ttyUSB0 using an
IOGear serial to USB converter. My system HARD hung.
I rebooted. In launching Evolution, all my previous pilot
settings were lost, and during reestablishing them,
gpilot crashed.



Debugging Information:

[New Thread 1024 (LWP 1295)]
0x406b6c09 in __wait4 () from /lib/libc.so.6

+ Trace 15682

Thread 1 (Thread 1024 (LWP 1295))

  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 strlen
    at ../sysdeps/i386/strlen.c line 28
  • #7 gpilotd_corba_get_pilots
    at orbit_daemon_glue.c line 1043
  • #8 _ORBIT_skel_GNOME_Pilot_Daemon_get_pilots
    at gnome-pilot-skels.c line 1973
  • #9 ORBit_POA_handle_request
    from /usr/lib/libORBit.so.0
  • #10 CORBA_ORB_run
    from /usr/lib/libORBit.so.0
  • #11 CORBA_ORB_run
    from /usr/lib/libORBit.so.0
  • #12 giop_main_handle_connection
    from /usr/lib/libIIOP.so.0
  • #13 orb_handle_connection
    from /usr/lib/libgnorba.so.27
  • #14 g_io_unix_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #15 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #16 g_main_iterate
    from /usr/lib/libglib-1.2.so.0
  • #17 g_main_iteration
    from /usr/lib/libglib-1.2.so.0
  • #18 wait_for_sync_and_sync
    at gpilotd.c line 1053
  • #19 main
    at gpilotd.c line 1116
  • #20 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/libc.so.6
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 strlen
    at ../sysdeps/i386/strlen.c line 28
  • #7 gpilotd_corba_get_pilots
    at orbit_daemon_glue.c line 1043 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-01-02 10:58 -------

Reassigning to the default owner of the component, eskil@eskil.dk.
Comment 1 kern 2002-01-02 16:41:03 UTC 
I'm upgrading this bug report to severity "blocker"
because I am now unable to connect my Palm. Every attempt
results in the same crash with a 0 being passed to strlen().

I've tried the following:
- Force reload of :
  gnome-pilot-0.1.63-ximian.2.i386.rpm
  gnome-pilot-devel-0.1.63-ximian.2.i386.rpm
  pilot-link-0.9.5-ximian.2.i386.rpm
  pilot-link-devel-0.9.5-ximian.2.i386.rpm

- Delete directory  ~kern/.gnome/gnome-pilot.d

I always get the same result, no pilot link configured,
running the configuration crashed.
Comment 2 kern 2002-01-02 17:48:22 UTC 
I'm downgrading this to normal after finding a solution.

Solution:
- kill running gpilotd
- Download the ximian gnome-pilot source rpm
- install the rpm
- detar the tarfile
  didn't apply two patches
- ./configure
- make
- cd gpilotd
- ./gpilotd
- rerun pilot configuration from Control Center
- kill my version of gpilotd

It now works. I don't understand why. Apparently the
gpilotd script in the build directory cleans up
something that the /usr/bin/gpilotd does not.
[kern@rufus gpilotd]$ ./gpilotd
gpilotd-Message: gnome-pilot 0.1.63 starting...
gpilotd-Message: compiled for pilot-link version 0.9.5
gpilotd-Message: compiled with [GOAD] [USB] [IrDA] [Network] 

gpilotd-WARNING **: Number of devices is configured to 0

gpilotd-WARNING **: No accessible devices available

gpilotd-WARNING **: Number of pilots is configured to 0
gpilotd-Message: Activating CORBA server
gpilotd-Message: Shutting down devices
gpilotd-Message: Rereading configuration...
gpilotd-Message: Watching Cradle (/dev/pilot)
gpilotd-Message: gpilotd: corba:
get_user_info(cradle=Cradle,survival=0,timeout=0)
gpilotd-Message: gpilotd: assigned handle num 9
gpilotd-Message: FISK: OST
gpilotd-Message: gpilotd: gpc_queue_purge_request()
gpilotd-Message: Shutting down devices
gpilotd-Message: Rereading configuration...
gpilotd-Message: Watching Cradle (/dev/ttyS0)
gpilotd-Message: gpilotd: corba:
get_user_info(cradle=Cradle,survival=0,timeout=0)
gpilotd-Message: gpilotd: assigned handle num 9
gpilotd-Message: Woke on Cradle
gpilotd-Message: setting PILOTRATE=115200

...

Output from running ./gpilotd
Comment 3 Luis Villa 2002-02-01 02:04:50 UTC 

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