Bug 251195 – Crash on new task

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 251195 - Crash on new task


Summary:	Crash on new task


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	1.5.x (obsolete)
Hardware:	Other All

Importance:	Normal major
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	251314 (view as bug list)
Depends on:
Blocks:

Reported:	2003-11-20 05:05 UTC by Gerardo Marin
Modified:	2013-09-10 14:03 UTC

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

Description Gerardo Marin 2003-11-20 05:05:56 UTC

Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:



Steps to reproduce the problem:
1. Go to tasks. 
2. Click on "New" button.

Actual Results:
Crash

Expected Results:


How often does this happen? 
ALways

Additional Information:

Backtrace was generated from '/usr/bin/evolution-1.5'

[New Thread 1093346720 (LWP 25386)]
[New Thread 1169079600 (LWP 25417)]
[New Thread 1158913328 (LWP 25416)]
[New Thread 1150520624 (LWP 25394)]
[New Thread 1142127920 (LWP 25393)]
[New Thread 1133735216 (LWP 25392)]
[New Thread 1125342512 (LWP 25391)]
[New Thread 1116949808 (LWP 25390)]
[New Thread 1106976048 (LWP 25389)]
0xffffe002 in ?? ()

+ Trace 41925

Thread 1 (Thread 1093346720 (LWP 25386))

#0 ??
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 segv_redirect
at main.c line 482
#3 <signal handler called>
#4 g_strdup
from /usr/lib/libglib-2.0.so.0
#5 e_comp_editor_registry_add
at e-comp-editor-registry.c line 126
#6 impl_requestCreateItem
at tasks-component.c line 576
#11 combo_button_activate_default_callback
at e-user-creatable-items-handler.c line 580
#12 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#17 impl_released
at e-combo-button.c line 373
#18 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#19 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#25 _gtk_button_paint
from /usr/lib/libgtk-x11-2.0.so.0
#26 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#32 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#35 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#36 unblock_source
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#38 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#39 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#40 bonobo_main
from /usr/lib/libbonobo-2.so.0
#41 main
at main.c line 620
#42 __libc_start_main
from /lib/tls/libc.so.6
#0 ??

Comment 1 Gerardo Marin 2003-11-28 20:51:53 UTC

*** bug 251314 has been marked as a duplicate of this bug. ***

Comment 2 JP Rosevear 2003-12-03 17:12:43 UTC

Caused by not having a primary selection set, which we handle now.