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 387862 - evolution crash when adding a new event
evolution crash when adding a new event
Status: RESOLVED DUPLICATE of bug 322624
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-12-20 10:59 UTC by mennucc1
Modified: 2007-01-07 16:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description mennucc1 2006-12-20 10:58:03 UTC 
Distribution: Debian 4.0
Package: Evolution
Severity: Normal
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Debian
Synopsis: evolution crash when adding a new event
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
an evolution component crash when adding a new event thru the date panel
applet

Steps to reproduce the crash:
1. click on the time in the gnome panel
2. double click on a date box
3. evolution starts, and it a window appears, to let me add a new event,
but something crashes

Expected Results:
should work :-)

How often does this happen?
everytime

Additional Information:
I messed up with evolution settings a bit, since
- I use unison to sync my accounts, and I wanted to
     sync my calendars, so I symlinked the .ics files in a common dir
- we have a Communigate server here that should support 
   calendaring.... but I could never have evolution to access my
   calendar folder inside Communigate (it says "authorization denied, 
   but never asks for my password!)


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47781867338352 (LWP 10649)]
[New Thread 1074006368 (LWP 10650)]
(no debugging symbols found)
0x00002b75115fe00f in waitpid () from /lib/libpthread.so.0

+ Trace 95648

Thread 1 (Thread 47781867338352 (LWP 10649))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_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 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #8 alarm_queue_init
  • #9 alarm_add
  • #10 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 waitpid
    from /lib/libpthread.so.0 




------- Bug created by bug-buddy at 2006-12-20 10:59 -------
Comment 1 palfrey 2007-01-07 16:39:54 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 322624 ***