Bug 336119 – Crash when right clicking on any set Rendez Vous in Calendar

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 336119 - Crash when right clicking on any set Rendez Vous in Calendar


Summary:	Crash when right clicking on any set Rendez Vous in Calendar


Status:	RESOLVED DUPLICATE of bug 312460

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-03-26 22:10 UTC by Damien Laniel
Modified:	2006-03-26 22:35 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description Damien Laniel 2006-03-26 22:10:12 UTC

Distribution: Debian testing/unstable
Package: Evolution
Severity: Normal
Version: GNOME2.12.3 unspecified
Gnome-Distributor: Debian
Synopsis: Crash when right clicking on any set Rendez Vous in Calendar
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.1)
Description:
Description of the crash:

Straightforward, hazardless and deadly

Steps to reproduce the crash:
1. Enter a new rendez vous
2. Validate it
3. Right click on it

Expected Results:

Crash

How often does this happen?

Always

Additional Information:

None


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1096593472 (LWP 31415)]
[New Thread 1103268784 (LWP 31417)]
(no debugging symbols found)
0x40ac1221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 67261

Thread 1 (Thread 1096593472 (LWP 31415))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 es_menu_hook_get_type
#3 <signal handler called>
#4 itip_get_comp_attendee
from /usr/lib/evolution/2.4/components/libevolution-calendar.so
#5 e_cal_popup_target_new_select
from /usr/lib/evolution/2.4/components/libevolution-calendar.so
#6 e_calendar_view_create_popup_menu
from /usr/lib/evolution/2.4/components/libevolution-calendar.so
#7 e_day_view_convert_time_to_position
from /usr/lib/evolution/2.4/components/libevolution-calendar.so
#8 e_day_view_convert_time_to_position
from /usr/lib/evolution/2.4/components/libevolution-calendar.so
#9 e_day_view_convert_time_to_position
from /usr/lib/evolution/2.4/components/libevolution-calendar.so
#10 e_day_view_convert_time_to_position
from /usr/lib/evolution/2.4/components/libevolution-calendar.so
#11 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#19 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 bonobo_main
from /usr/lib/libbonobo-2.so.0
#24 main
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0





------- Bug created by bug-buddy at 2006-03-26 22:10 -------

Comment 1 Sergej Kotliar 2006-03-26 22:35:17 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.

The stack trace is exactly the same as bug 315894, which is a duplicate of bug 312460.

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