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 328981 - Before appearing alarm(?) dialog, evolution-alarm-notify crashes.
Before appearing alarm(?) dialog, evolution-alarm-notify crashes.
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-28 16:41 UTC by sangu
Modified: 2013-09-13 00:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sangu 2006-01-28 16:41:46 UTC 
Please describe the problem:
Backtrace was generated from '/usr/libexec/evolution-alarm-notify'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208551760 (LWP 10216)]
[New Thread -1211819104 (LWP 10217)]
0x00560402 in ?? ()

+ Trace 65699

Thread 1 (Thread -1208551760 (LWP 10216))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_init_with_popt_table
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 free
    from /lib/libc.so.6
  • #5 IA__g_free
    at gmem.c line 187
  • #6 alarm_trigger_cb
    at alarm-queue.c line 1477 

Steps to reproduce:
1. setup alaram on calendar
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
always

Other information:
Fedora rawhide, arch x86
gtk2-2.8.11-1
glib2-2.9.5-1
evolution-2.5.5.1-2
evolution-data-server-1.5.5-1
libgnome-2.13.7-3
libgnomeui-2.13.3-1
libbonobo-2.13.1-8
libbonoboui-2.13.1-4
Comment 1 Christian Kirbach 2006-01-29 23:18:44 UTC 
unique and good trace, confirmin.
Comment 2 Chenthill P 2006-01-30 07:16:53 UTC 
Not yet confirmed :)
Comment 3 Poornima 2006-06-06 10:03:04 UTC 
Alarm daemon rewritten code will be having fix for this bug, fix is in head evolution 2.7.x. Better to verify in evolution 2.8 and update this bug.
Comment 4 sangu 2006-06-10 05:24:09 UTC 
This problem was fixed in evolution-devel-2.7.2.1.