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 479986 - crash in Evolution Mail: Clicked between two e-ma...
crash in Evolution Mail: Clicked between two e-ma...
Status: RESOLVED DUPLICATE of bug 426496
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-24 21:50 UTC by debian
Modified: 2007-10-03 00:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description debian 2007-09-24 21:50:27 UTC 
What were you doing when the application crashed?
Clicked between two e-mail messages in seperate folders in evolution


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-486 #1 Wed Jul 11 03:17:09 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: tish
Icon Theme: gnome

Memory status: size: 224563200 vsize: 224563200 resident: 51609600 share: 19030016 rss: 51609600 rss_rlim: 4294967295
CPU usage: start_time: 1190559940 rtime: 22231 utime: 20564 stime: 1667 cutime:2 cstime: 15 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1234261824 (LWP 1574)]
[New Thread -1419428976 (LWP 9535)]
[New Thread -1402651760 (LWP 9533)]
[New Thread -1364046960 (LWP 1697)]
[New Thread -1345270896 (LWP 1634)]
[New Thread -1336853616 (LWP 1633)]
[New Thread -1250952304 (LWP 1614)]
[New Thread -1327785072 (LWP 1612)]
[New Thread -1302226032 (LWP 1609)]
[New Thread -1310614640 (LWP 1608)]
[New Thread -1285448816 (LWP 1602)]
[New Thread -1277060208 (LWP 1601)]
[New Thread -1267729520 (LWP 1600)]
[New Thread -1259340912 (LWP 1599)]
[New Thread -1240994928 (LWP 1597)]
0xb774fbf1 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 165196

Thread 1 (Thread -1234261824 (LWP 1574))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 segv_redirect
    at main.c line 427
  • #3 <signal handler called>
  • #4 ??
  • #5 html_object_get_left_margin
    at htmlobject.c line 1090
  • #6 get_lmargin
    at htmlcluev.c line 98
  • #7 html_cluev_do_layout
    at htmlcluev.c line 155
  • #8 html_object_calc_size
    at htmlobject.c line 1069
  • #9 html_engine_calc_size
    at htmlengine.c line 4967
  • #10 thaw_idle
    at htmlengine.c line 5554
  • #11 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at main.c line 611
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0 


----------- .xsession-errors (48883 sec old) ---------------------
Could not connect to mail.ladyanddragonsemporium.com: Connection timed out
(evolution:1574): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Could not connect to mail.toledoohioneighborhoodconcerns.com: Connection timed out
(evolution:1574): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Could not connect to mail.buckeye-express.com: Connection timed out
(evolution:1574): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Failed to read a valid greeting from POP server mail.buckeye-express.com
(evolution:1574): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Failed to read a valid greeting from POP server mail.buckeye-express.com
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-10-03 00:35:49 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 426496 ***