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 326959 - alarm-notify crashes after selection of calendar
alarm-notify crashes after selection of calendar
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other other
: High critical
: Future
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 331039 (view as bug list)
Depends on:
Blocks: 327508 327510
 
 
Reported: 2006-01-14 13:23 UTC by Fabrice Peix
Modified: 2013-09-13 00:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Fabrice Peix 2006-01-14 13:23:15 UTC 
Distribution: Ubuntu 6.04 (dapper)
Package: Evolution
Severity: critical
Version: GNOME2.13.4 2.5.x
Gnome-Distributor: Ubuntu
Synopsis: alarm-notify bug. It seems that this appli crash
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.5.x
BugBuddy-GnomeVersion: 2.0 (2.13.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/libexec/evolution-alarm-notify'

(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 -1231481152 (LWP 7327)]
[New Thread -1234154576 (LWP 7328)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 65202

Thread 1 (Thread -1231481152 (LWP 7327))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 free
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_free
    from /usr/lib/libglib-2.0.so.0
  • #6 add_alarm_to_notified_alarms_dialog
  • #7 add_alarm_to_notified_alarms_dialog
  • #8 GNOME_Evolution_Calendar_CompEditorFactory_editNew
  • #9 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #14 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-01-14 13:23 -------
Comment 1 Luis Villa 2006-01-20 15:28:29 UTC 
I got the same trace when I clicked on the 'local' calendar in the notification icon of the latest build- an alarm window appeared after the click, and then the app crashed immediately.
Comment 2 Poornima 2006-02-14 04:59:48 UTC 
*** Bug 331039 has been marked as a duplicate of this bug. ***
Comment 3 Luis Villa 2006-02-19 17:28:54 UTC 
Got this again randomly today- no calendar manipulation; looks like an appointment was popping up (perhaps from a webcal.)
Comment 4 Poornima 2006-05-05 04:19:52 UTC 
Marking this as 'Nedinfo' as alarm crash has reduced drastically after sragavan has modified alarm deamon code. Code should is available in evolution 2.6.1, if bug is reproducible in 2.6.1, reopen this bug.
Comment 5 André Klapper 2006-06-11 17:30:17 UTC 
poornima: wrong, sorry. srini's ethread rewrite code is only available in the unstable 2.7, but not in the stable 2.6 branch as one can clearly see in cvs.

fabrice: any chance that you re-test this with the current unstable (!) evolution 2.7.2.1 or later version?
Comment 6 André Klapper 2006-10-02 08:49:19 UTC 
removing ancient gnome target milestone as it is unclear whether this issue is still around in 2.8, and there has been a rewrite of the code - fabrice, luis?
i would appreciate any updates on this bug report. thanks in advance.
Comment 7 Tobias Mueller 2008-02-29 20:55:10 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!