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 438415 - crash in Evolution: 1. Send encrypted email ...
crash in Evolution: 1. Send encrypted email ...
Status: RESOLVED DUPLICATE of bug 315012
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-05-14 19:36 UTC by Øystein Gisnås
Modified: 2007-06-03 21:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Øystein Gisnås 2007-05-14 19:36:33 UTC
What were you doing when the application crashed?
1. Send encrypted email
2. Go to sent mail and click to edit the sent, encrypted email

First reported by Nils Thieme and Viktor Horvath at http://bugs.debian.org/406664


Distribution: Debian lenny/sid
Gnome Release: 2.18.1 2007-04-25 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-1-686 #1 SMP Tue Apr 24 21:52:11 UTC 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: 106422272 vsize: 106422272 resident: 35770368 share: 20672512 rss: 35770368 rss_rlim: 4294967295
CPU usage: start_time: 1179171207 rtime: 314 utime: 232 stime: 82 cutime:1 cstime: 0 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 -1232176544 (LWP 23818)]
[New Thread -1269683312 (LWP 23838)]
[New Thread -1297118320 (LWP 23830)]
[New Thread -1288725616 (LWP 23829)]
[New Thread -1278076016 (LWP 23828)]
[New Thread -1261290608 (LWP 23823)]
[New Thread -1243354224 (LWP 23822)]
[New Thread -1252140144 (LWP 23821)]
0xb7fd87f2 in ?? () from /lib/ld-linux.so.2


----------- .xsession-errors ---------------------
(evolution-2.10:23439): Pango-CRITICAL **: pango_context_get_metrics: assertion `PANGO_IS_CONTEXT (context)' failed
(evolution-2.10:23439): Pango-CRITICAL **: pango_font_metrics_get_ascent: assertion `metrics != NULL' failed
(evolution-2.10:23439): Pango-CRITICAL **: pango_font_metrics_get_descent: assertion `metrics != NULL' failed
(evolution-2.10:23439): camel-CRITICAL **: camel_medium_get_content_object: assertion `CAMEL_IS_MEDIUM (medium)' failed

(gnome-terminal:23710): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Advarsel fra vindushåndterer: last_user_time (3079398448) is greater than comparison timestamp (2350035994).  This most likely represents a buggy client sending inaccurate timestamps in messages such
Advarsel fra vindushåndterer: 0x440000d (Terminal) appears to be one of the offending windows with a timestamp of 3079398448.  Working around...
(evolution-2.10:23818): camel-CRITICAL **: camel_medium_get_content_object: assertion `CAMEL_IS_MEDIUM (medium)' failed
--------------------------------------------------
Comment 1 Øystein Gisnås 2007-05-14 19:39:28 UTC
Sorry for posting the dupe. This is already reported at #315012.
Comment 2 palfrey 2007-05-15 13:28:29 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.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 3 Øystein Gisnås 2007-06-03 19:53:03 UTC
I have actually installed packages with debug symbols for libc6, libglib-2.0, evolution-data-server and evolution.

The most important here is to merge the bug with #315012.
Comment 4 palfrey 2007-06-03 21:15:28 UTC
Fair enough. There's not enough information in the stacktrace to actually narrow it down to being a duplicate, but as you're sure I'm marking it as such.

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