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 70222 - Memopad synchronization via gnome-pilot
Memopad synchronization via gnome-pilot
Status: RESOLVED DUPLICATE of bug 66247
Product: gnome-pilot
Classification: Other
Component: conduit: memo_file
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-01-31 23:32 UTC by alex
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description alex 2002-01-31 23:18:43 UTC 
Package: gnome-pilot
Severity: normal
Version: 0.1.64
Synopsis: Memopad synchronization via gnome-pilot
Bugzilla-Product: gnome-pilot
Bugzilla-Component: conduit: memo_file

Description:
When I try to enable memopad syncronization with my palm, gnome-pilot
dies.



Debugging Information:

(no debugging symbols found)...[New Thread 1024 (LWP 1586)]
0x406e9ca9 in __wait4 ()
   from /lib/i686/libc.so.6

+ Trace 17128

Thread 1 (Thread 1024 (LWP 1586))

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 659
  • #3 pthread_sighandler
    at signals.c line 97
  • #4 <signal handler called>
  • #5 load_configuration
    from /usr/lib/gnome-pilot/conduits/libmemo_file_conduit.so
  • #6 conduit_get_gpilot_conduit
    from /usr/lib/gnome-pilot/conduits/libmemo_file_conduit.so
  • #7 gnome_pilot_conduit_management_instantiate_conduit
    at gnome-pilot-conduit-management.gob line 720
  • #8 gnome_pilot_conduitcap_update
  • #9 gnome_pilot_conduitcap_update
  • #10 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #11 gtk_handlers_run
    at gtksignal.c line 1917
  • #12 gtk_signal_real_emit
    at gtksignal.c line 1477
  • #13 gtk_signal_emit
    at gtksignal.c line 552
  • #14 gtk_button_clicked
    at gtkbutton.c line 336
  • #15 gtk_real_button_released
    at gtkbutton.c line 861
  • #16 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #17 gtk_signal_real_emit
    at gtksignal.c line 1440
  • #18 gtk_signal_emit
    at gtksignal.c line 552
  • #19 gtk_button_released
    at gtkbutton.c line 327
  • #20 gtk_button_button_release
    at gtkbutton.c line 721
  • #21 gtk_marshal_BOOL__POINTER
    at gtkmarshal.c line 28
  • #22 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #23 gtk_signal_emit
    at gtksignal.c line 552
  • #24 gtk_widget_event
    at gtkwidget.c line 2864
  • #25 gtk_propagate_event
    at gtkmain.c line 1378
  • #26 gtk_main_do_event
    at gtkmain.c line 818
  • #27 gdk_event_dispatch
    at gdkevents.c line 2139
  • #28 g_main_dispatch
    at gmain.c line 656
  • #29 g_main_iterate
    at gmain.c line 877
  • #30 g_main_run
    at gmain.c line 935
  • #31 gtk_main
    at gtkmain.c line 524
  • #32 capplet_corba_gtk_main
    from /usr/lib/libcapplet.so.0
  • #33 capplet_gtk_main
    from /usr/lib/libcapplet.so.0
  • #34 main
  • #35 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 659
  • #3 pthread_sighandler
    at signals.c line 97
  • #4 <signal handler called>
  • #5 load_configuration
    from /usr/lib/gnome-pilot/conduits/libmemo_file_conduit.so
  • #6 conduit_get_gpilot_conduit
    from /usr/lib/gnome-pilot/conduits/libmemo_file_conduit.so
  • #7 gnome_pilot_conduit_management_instantiate_conduit
    at gnome-pilot-conduit-management.gob line 720 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-01-31 18:18 -------

The original reporter (alex@yucc.yorku.ca) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, eskil@eskil.dk.
Comment 1 Luis Villa 2002-02-01 03:48:55 UTC 

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