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 68253 - Repeated bug?
Repeated bug?
Status: RESOLVED DUPLICATE of bug 53967
Product: gnome-pilot
Classification: Other
Component: conduit system
unspecified
Other other
: Normal critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
: 82034 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-01-08 13:56 UTC by davidpurdy
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description davidpurdy 2002-01-08 13:56:55 UTC
Package: gnome-pilot
Severity: normal
Version: 0.1.63
Synopsis: Repeated bug?
Bugzilla-Product: gnome-pilot
Bugzilla-Component: conduit system

Description:
This caused gpilotd to crash, I believe.

I went to the gnome-pilot conduits (from "Pilot Settings" in Evolution),
went to Pilot Conduits, noticed nothing was displayed, same for Pilot
Link, and then clicked "Enable" (even though there were no conduits yet
added for enabling :)).

David



Debugging Information:

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

Thread 1 (Thread 1024 (LWP 19268))

  • #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
    at gnome-init.c line 659
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 get_current_state
    at gnome-pilot-conduitcap.c line 446
  • #7 gpcc_conduits_enable
    at gnome-pilot-conduitcap.c line 499
  • #8 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #9 gtk_handlers_run
    at gtksignal.c line 1917
  • #10 gtk_signal_real_emit
    at gtksignal.c line 1477
  • #11 gtk_signal_emit
    at gtksignal.c line 552
  • #12 gtk_button_clicked
    at gtkbutton.c line 336
  • #13 gtk_real_button_released
    at gtkbutton.c line 861
  • #14 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #15 gtk_signal_real_emit
    at gtksignal.c line 1440
  • #16 gtk_signal_emit
    at gtksignal.c line 552
  • #17 gtk_button_released
    at gtkbutton.c line 327
  • #18 gtk_button_button_release
    at gtkbutton.c line 721
  • #19 gtk_marshal_BOOL__POINTER
    at gtkmarshal.c line 28
  • #20 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #21 gtk_signal_emit
    at gtksignal.c line 552
  • #22 gtk_widget_event
    at gtkwidget.c line 2864
  • #23 gtk_propagate_event
    at gtkmain.c line 1378
  • #24 gtk_main_do_event
    at gtkmain.c line 818
  • #25 gdk_event_dispatch
    at gdkevents.c line 2139
  • #26 g_main_dispatch
    at gmain.c line 656
  • #27 g_main_iterate
    at gmain.c line 877
  • #28 g_main_run
    at gmain.c line 935
  • #29 gtk_main
    at gtkmain.c line 524
  • #30 capplet_corba_gtk_main
    at capplet-widget-libs.c line 140
  • #31 capplet_gtk_main
    at capplet-widget.c line 208
  • #32 main
    at gpilotd-control-applet.c line 173
  • #33 __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
    at gnome-init.c line 659
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 get_current_state
    at gnome-pilot-conduitcap.c line 446
  • #7 gpcc_conduits_enable
    at gnome-pilot-conduitcap.c line 499




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

The original reporter (davidpurdy@yahoo.com) 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 Heath Harrelson 2002-07-27 16:00:54 UTC
*** Bug 82034 has been marked as a duplicate of this bug. ***
Comment 2 Ben FrantzDale 2002-10-23 02:29:53 UTC
This appears to be a dup of bug 65148 which is a dup of bug 53967.

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