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 325508 - Crash clicking on e-a-n panel icon
Crash clicking on e-a-n panel icon
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
3.6.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 335501 (view as bug list)
Depends on:
Blocks: 327508 327510
 
 
Reported: 2006-01-02 13:45 UTC by Luke Hutchison
Modified: 2018-12-12 14:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Luke Hutchison 2006-01-02 13:45:26 UTC
Distribution: Unknown
Package: Evolution
Severity: critical
Version: GNOME2.13.3 2.5.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Crash clicking on e-a-n panel icon
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.5.x
BugBuddy-GnomeVersion: 2.0 (2.13.0)
Description:
Description of the crash:
I saw I had two alarms (the new e-a-n panel icon had a flashing
exclamation mark).  I double-clicked on the icon and got this crash as
the "Appointments" window was trying to draw itself.  This hasn't
happened before since I upgraded to Evolution 2.5.2 a few days ago.



Debugging Information:

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 -1208858432 (LWP 9059)]
[New Thread -1210958928 (LWP 9060)]
0x0097d402 in ?? ()

Thread 1 (Thread -1208858432 (LWP 9059))

  • #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 lookup_queued_alarm
    at alarm-queue.c line 244




------- Bug created by bug-buddy at 2006-01-02 13:45 -------

Comment 1 Christian Kirbach 2006-01-02 16:36:34 UTC
unique stack trace.

excellent trace, confirming
Comment 2 Veerapuram Varadhan 2006-02-21 14:05:30 UTC
I guess, this is fixed in CVS Head.  

@Luke: Can you try with CVS Head and confirm if it still happens?
Comment 3 Luke Hutchison 2006-02-21 14:45:43 UTC
Yes, this appears fixed, I haven't seen it again.  Thanks!
Comment 4 Karsten Bräckelmann 2006-03-23 15:24:57 UTC
*** Bug 335501 has been marked as a duplicate of this bug. ***
Comment 5 Luke Hutchison 2006-03-23 17:14:12 UTC
I have seen this again with FC5 rpms from FC5-development, with the same version numbers as those in FC5-final (as covered in the dup).  Re-opening so that there is one instance of this bug open.  I have seen this several times recently.  There is no e-d-s 1.6.0 available for FC5 yet in either the updates or development channels.
Comment 6 Poornima 2006-06-06 09:04:50 UTC
sragavan has rewritten alarm deamon code and committed in head 2.7.x. Marking this as 'Needinfo' to verify in evolution 2.8.
Comment 7 André Klapper 2006-11-01 10:53:37 UTC
marcus, did you have a chance to update to Evolution 2.8 yet?
Comment 8 Christian Kirbach 2007-02-22 21:29:51 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!
Comment 9 Milan Crha 2010-12-17 08:57:51 UTC
I'm reopening this, because we've a similar crash in 2.32.1 of evolution, filled as a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=663875
Comment 10 Milan Crha 2010-12-17 08:58:37 UTC
Core was generated by `/usr/libexec/evolution/2.32/evolution-alarm-notify'.
Program terminated with signal 11, Segmentation fault.

Thread 1 (Thread 13965)

  • #0 lookup_queued_alarm
    at alarm-queue.c line 300
  • #1 open_alarm_dialog
    at alarm-queue.c line 1297
  • #2 tray_icon_clicked_cb
    at alarm-queue.c line 1341
  • #3 icon_activated
    at alarm-queue.c line 1365
  • #4 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 79
  • #5 g_closure_invoke
    at gclosure.c line 766
  • #6 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #7 g_signal_emit_valist
    at gsignal.c line 2983
  • #8 g_signal_emit
    at gsignal.c line 3040
  • #9 emit_activate_signal
    at gtkstatusicon.c line 1282
  • #10 gtk_status_icon_button_press
    at gtkstatusicon.c line 1767
  • #11 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 86
  • #12 g_closure_invoke
    at gclosure.c line 766
  • #13 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #14 g_signal_emit_valist
    at gsignal.c line 2993
  • #15 g_signal_emit
    at gsignal.c line 3040
  • #16 gtk_widget_event_internal
    at gtkwidget.c line 4992
  • #17 IA__gtk_propagate_event
    at gtkmain.c line 2460
  • #18 IA__gtk_main_do_event
    at gtkmain.c line 1626
  • #19 gdk_event_dispatch
    at gdkevents-x11.c line 2377
  • #20 g_main_dispatch
    at gmain.c line 2149
  • #21 g_main_context_dispatch
    at gmain.c line 2702
  • #22 g_main_context_iterate
    at gmain.c line 2780
  • #23 g_main_loop_run
    at gmain.c line 2988
  • #24 IA__gtk_main
    at gtkmain.c line 1237
  • #25 main
    at notify-main.c line 118

Comment 11 Milan Crha 2011-05-09 06:44:56 UTC
Downstream bug report from Evolution 3.0.1:
https://bugzilla.redhat.com/show_bug.cgi?id=702810
Comment 12 André Klapper 2011-05-09 06:53:02 UTC
-> "See Also: Add Bug URLs:" field.
Comment 13 Milan Crha 2013-02-04 08:12:59 UTC
It seems to be still there, this time from 3.6.1:
https://bugzilla.redhat.com/show_bug.cgi?id=875525

Version-Release number of selected component:
evolution-3.6.1-1.fc18

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/3.6/evolution-alarm-notify
crash_function: lookup_queued_alarm
kernel:         3.6.6-3.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 lookup_queued_alarm at alarm-queue.c:328
: #1 open_alarm_dialog at alarm-queue.c:1438
: #2 tray_icon_clicked_cb at alarm-queue.c:1486
: #3 icon_activated at alarm-queue.c:1511
: #4 _g_closure_invoke_va at gclosure.c:840
: #7 emit_activate_signal at gtkstatusicon.c:1278
: #8 gtk_status_icon_button_press at gtkstatusicon.c:1604
: #9 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
: #14 gtk_widget_event_internal at gtkwidget.c:6301
: #15 gtk_widget_event at gtkwidget.c:5958
Comment 14 Milan Crha 2018-12-12 14:46:28 UTC
Thanks for a bug report. I'm closing this as obsolete, but feel free to reopen or comment in case you can reproduce with the current 3.30.x stable series.