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 271910 - Crash: Will not start
Crash: Will not start
Status: RESOLVED DUPLICATE of bug 271907
Product: evolution
Classification: Applications
Component: Calendar
2.0.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-01-28 15:48 UTC by jcook713
Modified: 2005-04-09 21:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jcook713 2005-01-28 15:48:39 UTC
Distribution: Debian 3.1
Package: Evolution
Priority: Normal
Version: GNOME2.8.1 2.0.3
Gnome-Distributor: Debian
Synopsis: Will not start
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.0.3
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Click on launcher icon and after a few seconds I get an error message
that evolution has unexpectedly quit.

Steps to reproduce the crash:
1. Turn on computer
2. click on evolution launcher
3. wait for error message

Expected Results:


How often does this happen?
every time

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.0'

(no debugging symbols found)...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)...[Thread debugging using
libthread_db enabled]
[New Thread 16384 (LWP 1357)]
[New Thread 32769 (LWP 1366)]
[New Thread 16386 (LWP 1367)]
[New Thread 32771 (LWP 1368)]
(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)...0x40e6fc0b in waitpid () from
/lib/libpthread.so.0
  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 ??
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 e_sidebar_get_type
  • #5 __pthread_sighandler
    from /lib/libpthread.so.0
  • #6 <signal handler called>
  • #7 realloc
    from /lib/ld-linux.so.2
  • #8 _dl_dst_substitute
    from /lib/ld-linux.so.2
  • #9 _dl_map_object
    from /lib/ld-linux.so.2
  • #10 getutmpx
    from /lib/libc.so.6
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 thread_self
    from /lib/libpthread.so.0



Unknown reporter: jcook713@gmail.com, 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 Olav Vitters 2005-04-09 21:20:06 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but the maintainers need more information to fix the
bug. Could you please answer the questions in the other report?

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