Bug 476575 – crash in Evolution:

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 476575 - crash in Evolution:


Summary:	crash in Evolution:


Status:	RESOLVED DUPLICATE of bug 426496

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-13 14:29 UTC by jesper
Modified:	2007-09-13 21:49 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description jesper 2007-09-13 14:29:10 UTC

What were you doing when the application crashed?



Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-15mdv #1 SMP Tue Aug 14 10:25:51 MDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 201457664 vsize: 201457664 resident: 33943552 share: 20676608 rss: 33943552 rss_rlim: 4294967295
CPU usage: start_time: 1189693782 rtime: 567 utime: 539 stime: 28 cutime:5 cstime: 6 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237190944 (LWP 4868)]
[New Thread -1332257888 (LWP 4946)]
[New Thread -1323037792 (LWP 4945)]
[New Thread -1314645088 (LWP 4944)]
[New Thread -1273656416 (LWP 4919)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 162628

Thread 1 (Thread -1237190944 (LWP 4868))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/libpthread.so.0
#2 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 html_object_get_left_margin
from /usr/lib/libgtkhtml-3.14.so.19
#5 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgtkhtml-3.14.so.19
#6 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgtkhtml-3.14.so.19
#7 html_object_calc_size
from /usr/lib/libgtkhtml-3.14.so.19
#8 html_engine_calc_size
from /usr/lib/libgtkhtml-3.14.so.19
#9 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgtkhtml-3.14.so.19
#10 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 bonobo_main
from /usr/lib/libbonobo-2.so.0
#15 main
#0 __kernel_vsyscall



----------- .xsession-errors (6 sec old) ---------------------
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
Initializing gnome-mount extension
/etc/menu.d/icewm: line 9: /home/jesper/.icewm/menu: Ingen sådan fil eller filkatalog
/etc/menu.d/icewm: line 16: /home/jesper/.icewm/menu: Ingen sådan fil eller filkatalog
run-parts: /etc/menu.d/icewm exited with return code 1
menu generation finished
SIOCETHTOOL: Operationen er ikke tilladt
SIOCETHTOOL: Operationen er ikke tilladt
SIOCETHTOOL: Operationen er ikke tilladt
SIOCETHTOOL: Operationen er ikke tilladt
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4868): DEBUG: mailto URL command: evolution %s
** (evolution:4868): DEBUG: mailto URL program: evolution
BBDB spinning up...
--------------------------------------------------

Comment 1 Pascal Terjan 2007-09-13 21:49:34 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 ***