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 472950 - crash in Evolution: evolution crashes on exi...
crash in Evolution: evolution crashes on exi...
Status: RESOLVED DUPLICATE of bug 472480
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-02 20:33 UTC by bugreports
Modified: 2007-09-03 16:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description bugreports 2007-09-02 20:33:21 UTC
What were you doing when the application crashed?
evolution crashes on exit


Distribution: Debian 3.1 (sarge)
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.23-rc5-sonne #47 SMP PREEMPT Sat Sep 1 10:17:22 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 204558336 vsize: 204558336 resident: 73879552 share: 25165824 rss: 73879552 rss_rlim: 4294967295
CPU usage: start_time: 1188737665 rtime: 10002 utime: 8509 stime: 1493 cutime:90 cstime: 34 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233167712 (LWP 6856)]
[New Thread -1398822000 (LWP 25521)]
[New Thread -1298437232 (LWP 27402)]
[New Thread -1306850416 (LWP 7142)]
[New Thread -1317016688 (LWP 7129)]
[New Thread -1308623984 (LWP 7128)]
[New Thread -1290019952 (LWP 7102)]
[New Thread -1281627248 (LWP 7048)]
[New Thread -1269830768 (LWP 7021)]
[New Thread -1261438064 (LWP 7018)]
[New Thread -1251533936 (LWP 7017)]
[New Thread -1243014256 (LWP 7009)]
0xb7fdd410 in __kernel_vsyscall ()

Thread 2 (Thread -1398822000 (LWP 25521))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_mutex_lock_86
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 segv_redirect
    at main.c line 436
  • #5 <signal handler called>
  • #6 ??
  • #7 folder_changed
    at camel-vee-folder.c line 1461
  • #8 camel_object_trigger_event
    at camel-object.c line 1511
  • #9 folder_changed_change
    at camel-vee-folder.c line 1422
  • #10 session_thread_proxy
    at camel-session.c line 530
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #15 ??
    from /usr/lib/libglib-2.0.so.0
  • #16 ??
  • #17 ??
  • #18 ??
    from /lib/i686/cmov/libc.so.6
  • #19 __elf_set___libc_atexit_element__IO_cleanup__
    from /lib/i686/cmov/libc.so.6
  • #20 __rpc_thread_destroy
    from /lib/i686/cmov/libc.so.6
  • #21 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #22 clone
    from /lib/i686/cmov/libc.so.6


----------- .xsession-errors (21 sec old) ---------------------
no fault of your own.
If you can reproduce the crash, please notify the developers
by reporting a bug at:
http://developer.pidgin.im/simpleticket/
Please make sure to specify what you were doing at the time
and post the backtrace from the core file.  If you do not know
how to get the backtrace, please read the instructions at
http://developer.pidgin.im/wiki/GetABacktrace
If you need further assistance, please IM either SeanEgn or 
LSchiere (via AIM).  Contact information for Sean and Luke 
on other protocols is at
http://developer.pidgin.im/wiki/DeveloperPages
--------------------------------------------------
Comment 1 palfrey 2007-09-03 16:57: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

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