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 521609 - crash in Evolution Mail: Atttempting to locate th...
crash in Evolution Mail: Atttempting to locate th...
Status: RESOLVED DUPLICATE of bug 520556
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.12.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
: 528155 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-03-10 16:32 UTC by rob.dawson
Modified: 2008-09-18 15:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description rob.dawson 2008-03-10 16:32:34 UTC 
What were you doing when the application crashed?
Atttempting to locate the debug packages for evolution for Bug 512605; This crash may or may not be related, but the trace looks different.

Further tracing probably requires debug packages being built for liborbit-2.0, and possibly libnm-glib0 and others.

I -think- the app was merely checking for new emails, but as I wasn't watching it at the time, I can't say for sure.


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686-bigmem #1 SMP Sun Feb 10 21:47:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Simple
Icon Theme: gnome

Memory status: size: 133201920 vsize: 133201920 resident: 39522304 share: 18124800 rss: 39522304 rss_rlim: 4294967295
CPU usage: start_time: 1205165811 rtime: 934 utime: 872 stime: 62 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb670e8e0 (LWP 9424)]
[New Thread 0xb1b6eb90 (LWP 9496)]
[New Thread 0xb24fcb90 (LWP 9491)]
[New Thread 0xb2cfdb90 (LWP 9490)]
[New Thread 0xb34feb90 (LWP 9454)]
[New Thread 0xb3cffb90 (LWP 9453)]
[New Thread 0xb46cbb90 (LWP 9452)]
[New Thread 0xb4eccb90 (LWP 9450)]
[New Thread 0xb56cdb90 (LWP 9449)]
[New Thread 0xb5eceb90 (LWP 9447)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 191983

Thread 10 (Thread 0xb5eceb90 (LWP 9447))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_lock_95
    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 422
  • #5 <signal handler called>
  • #6 exchange_get_folder_info
    at camel-exchange-store.c line 756
  • #7 camel_store_get_folder_info
    at camel-store.c line 790
  • #8 get_folderinfo_get
    at mail-ops.c line 1071
  • #9 mail_msg_received
    at mail-mt.c line 582
  • #10 thread_dispatch
    at e-msgport.c line 1005
  • #11 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #12 clone
    from /lib/i686/cmov/libc.so.6 


----------- .xsession-errors ---------------------
(gnome-panel:3309): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:3309): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:3309): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:3309): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:3309): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:3309): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:3309): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:3309): Wnck-WARNING **: Unhandled action type (nil)
--------------------------------------------------
Comment 1 Susana 2008-04-15 19:05:14 UTC 
*** Bug 528155 has been marked as a duplicate of this bug. ***
Comment 2 Milan Crha 2008-09-18 15:23:56 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 520556 ***