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 273635 - Crashing on start
Crashing on start
Status: RESOLVED DUPLICATE of bug 243160
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-03-12 22:43 UTC by amnonfeiner
Modified: 2005-04-09 23:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description amnonfeiner 2005-03-12 22:43:34 UTC
Package: Evolution
Priority: Normal
Version: 1.4.6
Synopsis: Crashing on start
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
BugBuddy-GnomeVersion: 2.0 (2.4.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 '/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 1094690752 (LWP 13494)]
[New Thread 1107106736 (LWP 13496)]
[Thread debugging using libthread_db enabled]
[New Thread 1094690752 (LWP 13494)]
[New Thread 1107106736 (LWP 13496)]
[New Thread 1105005488 (LWP 13495)]
(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 1094690752 (LWP 13494)]
[New Thread 1107106736 (LWP 13496)]
(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 1107106736 (LWP 13496))

  • #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: amnonfeiner@hotmail.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 Elijah Newren 2005-04-09 23:26:36 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.

Appears to match the stack trace in bug 265418, which has been marked as a
duplicate of 243160.

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