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 250278 - Evolution Crash on Startup
Evolution Crash on Startup
Status: RESOLVED DUPLICATE of bug 243160
Product: evolution
Classification: Applications
Component: Shell
pre-1.5 (obsolete)
Other All
: Normal major
: ---
Assigned To: Ettore Perazzoli
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-10-29 00:03 UTC by fred.hensley
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description fred.hensley 2003-10-29 00:03:10 UTC 
Package: Evolution
Priority: critical
Version: GNOME2.2.2 1.4.5
os_details: Ximian, Inc.
Synopsis: Evolution Crash on Startup
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
I just recently upgraded the internal memory for my x86 PC from 128MB to
512MB.  Now, intermittedly evolution crashes on startup due to a
segmentation fault.  Immediately restarting the program again usually
clears the program crash.

FYI - Memory checks indicate the new, expanded memory is workieng
flawlessly.

Steps to reproduce the problem:
1. Start Evolution
2. If program crashes on startup, there you go..
3. If program doesn't crash on startup, exit program and proceed to step
number one.

Actual Results:


Expected Results:


How often does this happen?

I would estimate once out of every 4-5 times I start evolution.

Additional Information:



Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 16384 (LWP 2663)]
[New Thread 32769 (LWP 2666)]
[New Thread 16386 (LWP 2667)]
[New Thread 32771 (LWP 2668)]

0x4010b844 in waitpid () from /lib/libpthread.so.0

+ Trace 41260

Thread 4 (Thread 32771 (LWP 2668))

  • #0 __pthread_sigsuspend
    from /lib/libpthread.so.0
  • #1 __pthread_wait_for_restart_signal
    from /lib/libpthread.so.0
  • #2 __pthread_alt_lock
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 evolution_storage_set_view_factory_new_view
  • #5 __pthread_sighandler
    from /lib/libpthread.so.0
  • #6 <signal handler called>
  • #7 do_lookup
    from /lib/ld-linux.so.2
  • #8 _dl_lookup_symbol_internal
    from /lib/ld-linux.so.2
  • #9 fixup
    from /lib/ld-linux.so.2
  • #10 _dl_runtime_resolve
    from /lib/ld-linux.so.2
  • #11 mail_msg_wait_all
    from /usr/lib/evolution/1.4/components/libevolution-mail.so
  • #12 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #13 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #14 pthread_start_thread
    from /lib/libpthread.so.0 



Unknown reporter: fred.hensley@comcast.net, 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 Gerardo Marin 2003-11-03 22:20:02 UTC 

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