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 521086 - crash in Email:
crash in Email:
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-03-07 21:03 UTC by snippet345
Modified: 2008-03-08 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description snippet345 2008-03-07 21:03:22 UTC 
Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 205676544 vsize: 205676544 resident: 64663552 share: 55779328 rss: 64663552 rss_rlim: 4294967295
CPU usage: start_time: 1204923670 rtime: 320 utime: 281 stime: 39 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 -1208334624 (LWP 2951)]
[New Thread -1351619696 (LWP 3078)]
[New Thread -1341129840 (LWP 3077)]
[New Thread -1258419312 (LWP 2975)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 191683

Thread 1 (Thread -1208334624 (LWP 2951))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (10 sec old) ---------------------
(evolution:2951): camel-pop3-provider-WARNING **: Bad server response: n15fo+Pqj2wP9iCBi4IB4Z+joHh56xMP4ADh2Zs4iT6H1olZlSl9b+qk5o90j3uIuXu/YxKGp5Ip
(evolution:2951): camel-pop3-provider-WARNING **: Bad server response: X-Yandex-Front: mxfront21X-Yandex-TimeMark: 1204853160
(evolution:2951): camel-pop3-provider-WARNING **: Bad server response: Received-SPF: none (mxfront21: 217.16.31.140 is neither permitted nor denied by domain of mail.SecurityLab.ru; fakespf=pass) clie
(evolution:2951): camel-pop3-provider-WARNING **: Bad server response: Received: from new_web ([217.16.31.136]) by mail.securitylab.ru with Microsoft SMTPSVC(6.0.3790.3959);
(evolution:2951): camel-pop3-provider-WARNING **: Bad server response:          Fri, 7 Mar 2008 04:25:52 +0300
--------------------------------------------------
Comment 1 Tobias Mueller 2008-03-08 20:07:25 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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