Bug 134946 – gcm Crashed

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 134946 - gcm Crashed


Summary:	gcm Crashed


Status:	RESOLVED DUPLICATE of bug 103742

Product:	gcm
Classification:	Deprecated
Component:	gcmapplet
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Philip Van Hoof
QA Contact:	Philip Van Hoof

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-02-20 17:19 UTC by Haixing Hu
Modified:	2004-12-22 21:47 UTC

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

Description Haixing Hu 2004-02-20 09:20:15 UTC

Distribution: Debian testing/unstable
Package: gcm
Severity: normal
Version: GNOME2.4.1 unspecified
Gnome-Distributor: Debian
Synopsis: gcm Crashed
Bugzilla-Product: gcm
Bugzilla-Component: gcmapplet
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
gcm crashed while I copy some text from emacs

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gcm'

(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[New Thread 16384 (LWP 1796)]
[New Thread 32769 (LWP 1797)]
[New Thread 16386 (LWP 1798)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x409a0bfb in waitpid () from /lib/libpthread.so.0

+ Trace 44395

Thread 1 (Thread 16384 (LWP 1796))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 ??
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/libpthread.so.0
#5 <signal handler called>
#6 g_type_free_instance
from /usr/lib/libgobject-2.0.so.0
#7 g_type_class_ref
from /usr/lib/libgobject-2.0.so.0
#8 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#9 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_object_new
from /usr/lib/libgobject-2.0.so.0
#11 gtk_type_new
from /usr/lib/libgtk-x11-2.0.so.0
#12 textitemwin_new
#13 app_create_and_show_textitemwin
#14 on_cliplistpopupmenu_edit_activate
#15 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#22 _gtk_menu_shell_activate
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_menu_reorder_child
from /usr/lib/libgtk-x11-2.0.so.0
#24 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#26 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#30 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#33 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#34 unblock_source
from /usr/lib/libglib-2.0.so.0
#35 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#37 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#0 waitpid
from /lib/libpthread.so.0





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-20 04:20 -------

Reassigning to the default owner of the component, me@freax.org.

Comment 1 Elijah Newren 2004-11-08 19:23:20 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.

Matches the stack trace in bug 125700, which has been marked as a duplicate of
103742.

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