Bug 345947 – Crashes when trying to modify a calendar entry by right clicking on the selected entry.

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 345947 - Crashes when trying to modify a calendar entry by right clicking on the selected entry.


Summary:	Crashes when trying to modify a calendar entry by right clicking on the selec...


Status:	RESOLVED DUPLICATE of bug 328985

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-06-26 10:19 UTC by jonna
Modified:	2006-07-04 11:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description jonna 2006-06-26 10:19:48 UTC

Distribution: Debian testing/unstable
Package: Evolution
Severity: Normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Debian
Synopsis: Crashes when trying to modify a calendar entry by right clicking on the selected entry.
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Crashes when trying to modify a calendar entry by right clicking on the
selected entry.

Steps to reproduce the crash:
1. Select the 14 of July 2006
2. Write an appointment at 1 pm
3. Right click on the appointment to modify the end time of the
appointment

Expected Results:
I wanted to change the end date of the appointment.

How often does this happen?
Only once, so far.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232082720 (LWP 4438)]
[New Thread -1301075024 (LWP 5832)]
[New Thread -1300235344 (LWP 4493)]
[New Thread -1290237008 (LWP 4469)]
[New Thread -1281844304 (LWP 4468)]
[New Thread -1273451600 (LWP 4456)]
[New Thread -1264096336 (LWP 4455)]
[New Thread -1255703632 (LWP 4449)]
[New Thread -1246917712 (LWP 4448)]
[New Thread -1238488144 (LWP 4446)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 69068





------- Bug created by bug-buddy at 2006-06-26 10:19 -------

Comment 1 Christian Kirbach 2006-06-26 15:22:35 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 jonna 2006-06-30 08:03:44 UTC

Hi! Sorry it took so long. Hope this is more useful.

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232877344 (LWP 4406)]
[New Thread -1307907152 (LWP 4467)]
[New Thread -1316299856 (LWP 4466)]
[New Thread -1265550416 (LWP 4455)]
[New Thread -1257157712 (LWP 4434)]
[New Thread -1256891472 (LWP 4417)]
[New Thread -1247220816 (LWP 4416)]
[New Thread -1238791248 (LWP 4414)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 69125

Thread 1 (Thread -1232877344 (LWP 4406))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 segv_redirect
at main.c line 424
#4 <signal handler called>
#5 e_cal_popup_target_new_select
at e-cal-popup.c line 572
#6 e_calendar_view_create_popup_menu
at e-calendar-view.c line 1668
#7 e_day_view_show_popup_menu
at e-day-view.c line 3299
#8 e_day_view_on_main_canvas_button_press
at e-day-view.c line 3018
#9 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#17 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 bonobo_main
from /usr/lib/libbonobo-2.so.0
#22 main
at main.c line 612
#0 __kernel_vsyscall

Comment 3 Christian Kirbach 2006-07-04 11:15:01 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.


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