Bug 75224 – Crash after selecting Palm "memo file" conduit

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 75224 - Crash after selecting Palm "memo file" conduit


Summary:	Crash after selecting Palm "memo file" conduit


Status:	RESOLVED DUPLICATE of bug 73294

Product:	gnome-pilot
Classification:	Other
Component:	conduit: memo_file
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gnome-pilot Maintainers
QA Contact:	gnome-pilot Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-03-18 06:49 UTC by David.Walker
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description David.Walker 2002-03-18 06:49:34 UTC

Package: gnome-pilot
Severity: normal
Version: 0.1.64
Synopsis: Crash after selecting Palm "memo file" conduit
Bugzilla-Product: gnome-pilot
Bugzilla-Component: conduit: memo_file

Description:
I had just installed Ximian's extra Palm conduits and had enabled MAL
and the time 
conduit.  When I clicked on the Memo File" conduit, this happened.



Debugging Information:

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

+ Trace 19355

Thread 1 (Thread 1024 (LWP 9259))

#0 __wait4
from /lib/libc.so.6
#1 __DTOR_END__
from /lib/libc.so.6
#2 gnome_segv_handle
at gnome-init.c line 664
#3 pthread_sighandler
at signals.c line 97
#4 <signal handler called>
#5 load_configuration
at memo_file_conduit.c line 88
#6 conduit_get_gpilot_conduit
at memo_file_conduit.c line 1430
#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/libc.so.6
#0 __wait4
from /lib/libc.so.6
#1 __DTOR_END__
from /lib/libc.so.6
#2 gnome_segv_handle
at gnome-init.c line 664
#3 pthread_sighandler
at signals.c line 97
#4 <signal handler called>
#5 load_configuration
at memo_file_conduit.c line 88
#6 conduit_get_gpilot_conduit
at memo_file_conduit.c line 1430
#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-03-18 01:49 -------

The original reporter (David.Walker@ucop.edu) 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 David.Walker 2002-03-18 07:23:11 UTC

Just to clarify...  The crash happened after I clicked on the "Enable"
button in the Gnome Conduits capplet after selecting the Memo File
conduit.  It didn't happen when I selected the conduit.

David

Comment 2 Håvard Wigtil 2002-03-18 14:47:32 UTC


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