Bug 455924 – crash in Tasks: I changed the size of my...

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 455924 - crash in Tasks: I changed the size of my...


Summary:	crash in Tasks: I changed the size of my...


Status:	RESOLVED DUPLICATE of bug 445067

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-11 14:30 UTC by Daniel Manley
Modified:	2007-07-12 11:14 UTC

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

Description Daniel Manley 2007-07-11 14:30:12 UTC

Version: 2.10

What were you doing when the application crashed?
I changed the size of my fonts from 10 to 9 points.


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

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 258256896 vsize: 258256896 resident: 169496576 share: 37261312 rss: 169496576 rss_rlim: 4294967295
CPU usage: start_time: 1184094284 rtime: 4003 utime: 3778 stime: 225 cutime:0 cstime: 2 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 -1208887584 (LWP 12094)]
[New Thread -1228129392 (LWP 12340)]
[New Thread -1249502320 (LWP 12122)]
[New Thread -1261442160 (LWP 12121)]
[New Thread -1238619248 (LWP 12119)]
(no debugging symbols found)
0x00ea1402 in __kernel_vsyscall ()

+ Trace 147266

Thread 1 (Thread -1208887584 (LWP 12094))

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



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libXdmcp.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libsoup-2.2.so.8" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgnutls.so.13" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libexchange-storage-1.2.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 palfrey 2007-07-12 11:14:32 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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