Bug 442059 – crash in Evolution: Starting the gnome font ...

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 442059 - crash in Evolution: Starting the gnome font ...


Summary:	crash in Evolution: Starting the gnome font ...


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-05-29 12:57 UTC by alexis.rohou
Modified:	2007-05-29 20:37 UTC

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

Description alexis.rohou 2007-05-29 12:57:23 UTC

What were you doing when the application crashed?
Starting the gnome font applet.


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

System: Linux 2.6.17-14mdv #1 SMP Wed May 9 21:09:44 MDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Free
Icon Theme: gnome

Memory status: size: 517513216 vsize: 517513216 resident: 52830208 share: 24064000 rss: 52830208 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180441263 rtime: 648 utime: 572 stime: 76 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46998818631072 (LWP 7258)]
[New Thread 1174718784 (LWP 10269)]
[New Thread 1141147968 (LWP 7425)]
[New Thread 1140881728 (LWP 7411)]
[New Thread 1132489024 (LWP 7410)]
[New Thread 1124096320 (LWP 7360)]
[New Thread 1115703616 (LWP 7359)]
[New Thread 1107310912 (LWP 7325)]
[New Thread 1098918208 (LWP 7321)]
[New Thread 1090525504 (LWP 7320)]
[New Thread 1082132800 (LWP 7318)]
0x00002abebf3eec2e in waitpid () from /lib64/libpthread.so.0

+ Trace 136627

Thread 1 (Thread 46998818631072 (LWP 7258))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__BOOLEAN
at gmarshal.c line 89
#2 <signal handler called>
#3 html_object_get_left_margin
from /usr/lib64/libgtkhtml-3.14.so.19
#4 g_cclosure_marshal_VOID__BOOLEAN
at gmarshal.c line 89
#5 g_cclosure_marshal_VOID__BOOLEAN
at gmarshal.c line 89
#6 html_object_calc_size
from /usr/lib64/libgtkhtml-3.14.so.19
#7 html_engine_calc_size
from /usr/lib64/libgtkhtml-3.14.so.19
#8 g_cclosure_marshal_VOID__BOOLEAN
at gmarshal.c line 89
#9 IA__g_main_context_dispatch
at gmain.c line 2045
#10 g_main_context_iterate
at gmain.c line 2677
#11 IA__g_main_loop_run
at gmain.c line 2881
#12 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#13 main
at main.c line 611
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
(evolution:7258): Gtk-CRITICAL **: gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed
** (gnome-cups-manager:7495): WARNING **: IPP request failed with status 1030
** (gnome-cups-manager:7495): WARNING **: IPP request failed with status 1030
** (gnome-cups-manager:7495): WARNING **: IPP request failed with status 1030
warning: the debug information found in "/usr/lib/debug//usr/lib64/evolution/2.10/components/libevolution-calendar.so.debug" does not match "/usr/lib64/evolution/2.10/components/libevolution-calendar.
** (gnome-cups-manager:7495): WARNING **: IPP request failed with status 1030
** (gnome-cups-manager:7495): WARNING **: IPP request failed with status 1030
--------------------------------------------------

Comment 1 Pascal Terjan 2007-05-29 20:37:40 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 426496 ***