Bug 274414 – "Edit Appointment" button does not work

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 274414 - "Edit Appointment" button does not work


Summary:	"Edit Appointment" button does not work


Status:	RESOLVED DUPLICATE of bug 310338

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	pre-1.5 (obsolete)
Hardware:	Other All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-04-05 15:31 UTC by Jeremy Davis
Modified:	2005-08-31 07:35 UTC

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

Description Jeremy Davis 2005-04-05 15:31:51 UTC

Distribution: Fedora Core release 2 (Tettnang)
Package: Evolution
Priority: Normal
Version: GNOME2.6. 1.4.6
Gnome-Distributor: Red Hat, Inc
Synopsis: "Edit Appointment" button does not work
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 1.4.6
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
Meeting reminder popup crashes when "Edit Appointment" is selected.

Steps to reproduce the crash:
1. Create and schedule a meeting. 
2. Receive popup reminder.
3. Select "Edit Appointment"

Expected Results:


How often does this happen?
Has happened twice.  I was able to reproduce it.

Additional Information:
The application does not crash, only the reminder.


Unknown reporter: jeremyrdavis@gmail.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Elijah Newren 2005-04-10 03:20:39 UTC

Thanks for the bug report. Without a stack trace from the crash it's very hard
to determine what caused it. Can you provide us with one? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Jeremy Davis 2005-04-13 12:53:02 UTC

I reproduced the crash this morning and got this from gdb:

+ Trace 58126

Thread 3 (Thread 45530032 (LWP 21856))

#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2
#1 pthread_cond_wait
from /lib/tls/libpthread.so.0
#2 e_msgport_wait
from /usr/lib/evolution/1.4/libeutil.so.0
#3 e_thread_busy
from /usr/lib/evolution/1.4/libeutil.so.0
#4 start_thread
from /lib/tls/libpthread.so.0
#5 clone
from /lib/tls/libc.so.6

Thread 2 (Thread 35040176 (LWP 21855))

#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2
#1 pthread_cond_wait
from /lib/tls/libpthread.so.0
#2 e_msgport_wait
from /usr/lib/evolution/1.4/libeutil.so.0
#3 e_thread_busy
from /usr/lib/evolution/1.4/libeutil.so.0
#4 start_thread
from /lib/tls/libpthread.so.0
#5 clone
from /lib/tls/libc.so.6

Thread 1 (Thread -1208712544 (LWP 21852))

#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2
#1 poll
from /lib/tls/libc.so.6
#2 g_main_loop_get_context
from /usr/lib/libglib-2.0.so.0
#3 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#4 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#5 bonobo_main
from /usr/lib/libbonobo-2.so.0
#6 main

Comment 3 viren 2005-08-23 09:28:08 UTC

The stack trace provided is not useful.Traces of the alarm-deamon is required.

Comment 4 Chenthill P 2005-08-31 07:35:45 UTC

This has been fixed.

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