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 251832 - Crash: Segmentation fault
Crash: Segmentation fault
Status: RESOLVED DUPLICATE of bug 243160
Product: evolution
Classification: Applications
Component: Shell
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-12-07 21:07 UTC by linux
Modified: 2004-03-22 22:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description linux 2003-12-07 21:07:55 UTC
Package: Evolution
Priority: Normal
Version: 1.4.5
Synopsis: Segmentation fault
Bugzilla-Product: Evolution
Bugzilla-Component: Shell
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:


Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




Debugging Information:

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

[New Thread 1093193056 (LWP 3946)]
[New Thread 1133742896 (LWP 3949)]
[New Thread 1125350192 (LWP 3948)]
[New Thread 1116957488 (LWP 3947)]
0xffffe002 in ?? ()

Thread 4 (Thread 1116957488 (LWP 3947))

  • #0 ??
  • #1 segv_redirect
    at main.c line 509
  • #2 <signal handler called>
  • #3 do_lookup
    from /lib/ld-linux.so.2
  • #4 _dl_lookup_symbol_internal
    from /lib/ld-linux.so.2
  • #5 fixup
    from /lib/ld-linux.so.2
  • #6 _dl_runtime_resolve
    from /lib/ld-linux.so.2
  • #7 mail_msg_received
    at mail-mt.c line 492
  • #8 thread_received_msg
    at e-msgport.c line 617
  • #9 thread_dispatch
    at e-msgport.c line 698
  • #10 start_thread
    from /lib/tls/libpthread.so.0


Unknown reporter: linux@uotips.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 Gerardo Marin 2004-03-22 22:50:50 UTC

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