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 273699 - Crash starting evolution-alarm-notify manually if it already runs
Crash starting evolution-alarm-notify manually if it already runs
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.12.x (obsolete)
Other All
: High critical
: Future
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 302084 321332 321659 324951 325488 326765 328511 328730 330128 330451 363523 374166 412626 443579 509466 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-03-14 23:58 UTC by Matthew Overy
Modified: 2013-09-13 00:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed hacky patch (1.15 KB, patch)
2007-07-20 12:09 UTC, Milan Crha
committed Details | Review

Description Matthew Overy 2005-03-14 23:58:24 UTC
Distribution: Debian 3.1
Package: Evolution
Priority: Normal
Version: GNOME2.10.0 2.2.0
Gnome-Distributor: Ubuntu
Synopsis: evolution-alarm-notify has terminated unexpectedly
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 2.2.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. install base warty system
2. dist upgrade to hoary
3. reboot machine and upon login the evolution-alarm-notify process
crashes unexpectedly

Expected Results:

It shouldn't do this!

How often does this happen?

Every login

Additional Information:



Debugging Information:

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

Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 183002562880 (LWP 8396)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x0000002a99337f86 in waitpid () from /lib/libc.so.6

Thread 1 (Thread 183002562880 (LWP 8396))

  • #0 waitpid
    from /lib/libc.so.6
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 main
  • #0 waitpid
    from /lib/libc.so.6



Unknown reporter: matthew.overy@blueyonder.co.uk, 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-09 23:27:51 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 Elijah Newren 2005-05-10 16:05:41 UTC
No response--closing; feel free to reopen if you can provide the requested
information.
Comment 3 Karsten Bräckelmann 2006-02-06 15:13:46 UTC
*** Bug 321332 has been marked as a duplicate of this bug. ***
Comment 4 Karsten Bräckelmann 2006-02-06 15:13:51 UTC
*** Bug 321659 has been marked as a duplicate of this bug. ***
Comment 5 Karsten Bräckelmann 2006-02-06 15:13:56 UTC
*** Bug 328730 has been marked as a duplicate of this bug. ***
Comment 6 Karsten Bräckelmann 2006-02-06 15:14:07 UTC
*** Bug 330128 has been marked as a duplicate of this bug. ***
Comment 7 Karsten Bräckelmann 2006-02-06 15:17:00 UTC
REOPENing and Confirming due to duplicates. Setting proper crasher priority.

Note: All duplicates are Evo 2.2.x.
Comment 8 Karsten Bräckelmann 2006-02-06 15:32:12 UTC
*** Bug 326765 has been marked as a duplicate of this bug. ***
Comment 9 Karsten Bräckelmann 2006-02-06 15:34:36 UTC
*** Bug 302084 has been marked as a duplicate of this bug. ***
Comment 10 Karsten Bräckelmann 2006-02-06 15:36:09 UTC
*** Bug 325488 has been marked as a duplicate of this bug. ***
Comment 11 Karsten Bräckelmann 2006-02-06 15:36:15 UTC
*** Bug 328511 has been marked as a duplicate of this bug. ***
Comment 12 Karsten Bräckelmann 2006-02-06 15:37:41 UTC
Some more duplicates.

Note: One of the duplicates is Evo 2.0.x, that last two duplucates are actually Evolution 2.4.x!
Comment 13 Karsten Bräckelmann 2006-02-08 18:50:59 UTC
*** Bug 330451 has been marked as a duplicate of this bug. ***
Comment 14 Karsten Bräckelmann 2006-02-08 18:52:24 UTC
Another 2.4.x duplicate. Correcting Component, setting Target Milestone.
Comment 15 Karsten Bräckelmann 2006-02-08 21:53:03 UTC
*** Bug 324951 has been marked as a duplicate of this bug. ***
Comment 16 Chenthill P 2006-02-09 14:31:27 UTC
The stack traces not informative. Please provide a better trace. Also try upgrading to the version 2.4.2.1 which has a similar bug 323955 fixed. Providing the warnings which appear by running evolution-alarm-notify from terminal will also be very useful.
Comment 17 Chenthill P 2006-02-10 05:23:37 UTC
I worked on this some of the crashes in alarm daemon. I saw it happening, 
this is because creation of a bonobo factory fails and a g_error log will be displayed in the terminal, "Could not create the alarm notify service factory". Reopening.
Comment 18 André Klapper 2006-06-11 21:50:29 UTC
would be nice to know if this is fixed in CVS head by srini's EThread alarm notify improvements... comments?
Comment 19 Srinivasa Ragavan 2006-06-12 05:20:02 UTC
Andre if chen is right, this should happen, if some one starts alarm notify manually and it is running automatically. this is not yet fixed.
Comment 20 André Klapper 2007-06-15 21:46:20 UTC
this STILL happens in 2.11, folks!


  • #3 <signal handler called>
  • #4 IA__g_logv
    at gmessages.c line 493
  • #5 IA__g_log
    at gmessages.c line 517
  • #6 main
    at notify-main.c line 153
  • #0 __kernel_vsyscall


----------- .xsession-errors (42 sec old) ---------------------
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-queue.c:2020 (alarm_queue_add_async) - 0x9e2e030
alarm-queue.c:585 (load_alarms_for_today) - From Sun Jun  3 00:00:00 2007
 to Sun Jun  3 00:00:00 2007
alarm-queue.c:522 (load_alarms) 
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-queue.c:2020 (alarm_queue_add_async) - 0x9e36720
alarm-queue.c:585 (load_alarms_for_today) - From Sun Jun  3 00:00:00 2007
 to Sun Jun  3 00:00:00 2007
alarm-queue.c:522 (load_alarms) 
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-notify.c:316 (cal_opened_cb)
file:///home/jik/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2020 (alarm_queue_add_async) - 0x9e39760
alarm-queue.c:585 (loa
--------------------------------------------------
Comment 21 André Klapper 2007-06-15 21:46:29 UTC
*** Bug 443579 has been marked as a duplicate of this bug. ***
Comment 22 André Klapper 2007-06-15 21:46:40 UTC
*** Bug 412626 has been marked as a duplicate of this bug. ***
Comment 23 André Klapper 2007-06-15 21:46:50 UTC
*** Bug 374166 has been marked as a duplicate of this bug. ***
Comment 24 André Klapper 2007-06-15 21:46:57 UTC
*** Bug 363523 has been marked as a duplicate of this bug. ***
Comment 25 Milan Crha 2007-07-20 12:09:04 UTC
Created attachment 92037 [details] [review]
proposed hacky patch

for evolution;

this is a hacky patch, it only changed g_error to g_warning when factory could not be created, and changed a string to "Could not create the alarm notify service factory, maybe it's already running...".

I did want to do it properly, with error code checking, but the bonobo didn't propagate this error code and it could not be rewrote, because used functions touch private member of factory in bonobo_generic_factory_construct.

I'm not sure if srag will not to rewrite this to not use bonobo as he mentioned at other place, so it will be fixed in better way.
Comment 26 Srinivasa Ragavan 2007-07-26 08:11:43 UTC
Milan. I think it is not a error condition at all. If it is already running you cause a warning and quit safely. I think this is perfectly OK. Also It would be fine to return 0 in this case as it is not a real error.
Comment 27 Milan Crha 2007-07-26 08:28:36 UTC
there's just a problem that you don't know if it fails because of real error or because it is already running, so I prefer to not return 0, just to indicate _possible_ error.
Comment 28 Srinivasa Ragavan 2007-07-26 08:39:42 UTC
go ahead :)
Comment 29 Milan Crha 2007-07-26 09:28:47 UTC
Committed to trunk, Committed revision 33843.
Comment 30 Milan Crha 2008-09-15 08:44:29 UTC
*** Bug 509466 has been marked as a duplicate of this bug. ***