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 329800 - evolution-alarm-notify crashed on startup
evolution-alarm-notify crashed on startup
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: Veerapuram Varadhan
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-02-03 16:09 UTC by Christopher Lee
Modified: 2013-09-13 00:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Christopher Lee 2006-02-03 16:09:35 UTC 
Distribution: Ubuntu 6.04 (dapper)
Package: Evolution
Severity: Normal
Version: GNOME2.13.90 2.5.x
Gnome-Distributor: Ubuntu
Synopsis: evolution-alarm-notify crashed on startup
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 2.5.x
BugBuddy-GnomeVersion: 2.0 (2.13.3)
Description:
Description of the crash:

After evolution-alarm-notify has opened all its calendar sources, it
prints the following error message to stdout and exits:

evolution-alarm-notify-ERROR **: Could not create the alarm notify
service factory
aborting...

Steps to reproduce the crash:

$ /usr/lib/evolution/2.6/evolution-alarm-notify

(Ubuntu Dapper)

How often does this happen?

Every time.

Additional Information:

/usr/lib/evolution/2.6/evolution-alarm-notify --version
Gnome evolution-alarm-notify 2.5.90



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 -1232001344 (LWP 10192)]
[New Thread -1233302608 (LWP 10193)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 65888

Thread 1 (Thread -1232001344 (LWP 10192))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    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 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #5 g_log
    from /usr/lib/libglib-2.0.so.0
  • #6 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-02-03 16:09 -------
Comment 1 André Klapper 2006-02-05 02:50:31 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, and if needed, install the appropriate devel packages so more debugging symbols will be included.
Comment 2 Karsten Bräckelmann 2006-02-28 20:52:55 UTC 
Reassigning some important 2.5.x bugs to Varadhan.
Comment 3 André Klapper 2006-06-11 17:07:54 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!