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 265418 - Crash: segment fault
Crash: segment fault
Status: RESOLVED DUPLICATE of bug 243160
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-09-07 05:35 UTC by reima
Modified: 2004-09-07 21:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description reima 2004-09-07 05:35:19 UTC
Distribution: SuSE Linux 9.1 (i586)
Package: Evolution
Priority: Normal
Version: GNOME2.4.1 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: segment fault
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:


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

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution-1.4'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/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)...[Thread debugging using
libthread_db enabled]
[New Thread 1094660256 (LWP 4604)]
[New Thread 1107127216 (LWP 4606)]
[Thread debugging using libthread_db enabled]
[New Thread 1094660256 (LWP 4604)]
[New Thread 1107127216 (LWP 4606)]
[Thread debugging using libthread_db enabled]
[New Thread 1094660256 (LWP 4604)]
[New Thread 1107127216 (LWP 4606)]
[New Thread 1105025968 (LWP 4605)]
(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)...0xffffe410 in ?? ()

Thread 2 (Thread 1107127216 (LWP 4606))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #5 _L_mutex_lock_33
    from /lib/tls/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 __JCR_LIST__
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 segv_redirect
  • #0 ??



Unknown reporter: reima@liljansaari.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-09-07 21:27:46 UTC

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