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 445989 - crash in Evolution Mail:
crash in Evolution Mail:
Status: RESOLVED DUPLICATE of bug 371529
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-06-10 10:17 UTC by patrick.kox
Modified: 2007-06-11 09:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description patrick.kox 2007-06-10 10:17:33 UTC
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-1-686 #1 SMP Sat May 26 16:14:59 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Brushed
Icon Theme: OSX

Memory status: size: 97656832 vsize: 97656832 resident: 29499392 share: 16855040 rss: 29499392 rss_rlim: 4294967295
CPU usage: start_time: 1181469887 rtime: 176 utime: 155 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232803232 (LWP 11594)]
[New Thread -1285440624 (LWP 11656)]
[New Thread -1294697584 (LWP 11652)]
[New Thread -1268663408 (LWP 11651)]
[New Thread -1249535088 (LWP 11636)]
[New Thread -1277052016 (LWP 11628)]
[New Thread -1257923696 (LWP 11626)]
[New Thread -1241146480 (LWP 11624)]
(no debugging symbols found)
0xb77a3b11 in ?? () from /lib/libpthread.so.0

Thread 2 (Thread -1285440624 (LWP 11656))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_mutex_lock_88
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #9 ??
  • #10 ??
  • #11 <signal handler called>
  • #12 camel_index_add_name
    from /usr/lib/libcamel-1.2.so.10
  • #13 camel_folder_summary_info_new_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #14 camel_folder_summary_add_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #15 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
  • #16 ??
  • #17 ??
  • #18 ??


----------- .xsession-errors (263 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Windowmanager waarschuwing:Ongeldig WM_TRANSIENT_FOR venster 0x65 opgegeven voor 0x140c6a9 ().
--------------------------------------------------
Comment 1 Susana 2007-06-10 17:50:06 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace, paste it as a
comment here and reopen this bug or just report a new one. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk,
glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided
by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 André Klapper 2007-06-11 09:11:44 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 371529 ***