Bug 353897 – crash in Evolution: I was entering a passwor...

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 353897 - crash in Evolution: I was entering a passwor...


Summary:	crash in Evolution: I was entering a passwor...


Status:	RESOLVED DUPLICATE of bug 349310

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Harish Krishnaswamy
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-01 20:50 UTC by Pascual Abellan
Modified:	2006-09-01 20:55 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Pascual Abellan 2006-09-01 20:50:31 UTC

What were you doing when the application crashed?
I was entering a password for an email account. I make a fresh install of ubuntu edgy, and I was trying to use old home and configurations files from ubuntu dapper. Hope this help and sorry for my english :p


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 394915840 vsize: 394915840 resident: 31039488 share: 19234816 rss: 31039488 rss_rlim: -1
CPU usage: start_time: 1157143471 rtime: 204 utime: 185 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 47443501828864 (LWP 14492)]
[New Thread 1149274448 (LWP 14615)]
[New Thread 1132489040 (LWP 14614)]
[New Thread 1157667152 (LWP 14612)]
[New Thread 1208289616 (LWP 14524)]
[New Thread 1208023376 (LWP 14523)]
[New Thread 1199630672 (LWP 14522)]
[New Thread 1191237968 (LWP 14520)]
[New Thread 1174452560 (LWP 14518)]
[New Thread 1166059856 (LWP 14517)]
[New Thread 1140881744 (LWP 14513)]
[New Thread 1124096336 (LWP 14511)]
[New Thread 1115703632 (LWP 14510)]
[New Thread 1098918224 (LWP 14508)]
[New Thread 1082132816 (LWP 14506)]
0x00002b2648fca6df in __libc_waitpid () from /lib/libc.so.6

+ Trace 71382

Thread 1 (Thread 47443501828864 (LWP 14492))

#0 __libc_waitpid
from /lib/libc.so.6
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 cairo_font_face_destroy
from /usr/lib64/libcairo.so.2
#4 cairo_font_options_copy
from /usr/lib64/libcairo.so.2
#5 pango_cairo_context_set_font_options
from /usr/lib64/libpangocairo-1.0.so.0
#6 e_cell_text_new
from /usr/lib/evolution/2.8/libetable.so.0
#7 e_cell_text_get_text_by_view
from /usr/lib/evolution/2.8/libetable.so.0
#8 e_cell_text_get_text_by_view
from /usr/lib/evolution/2.8/libetable.so.0
#9 e_table_item_set_cursor
from /usr/lib/evolution/2.8/libetable.so.0
#10 gnome_canvas_root
from /usr/lib64/libgnomecanvas-2.so.0
#11 gnome_canvas_item_new
from /usr/lib64/libgnomecanvas-2.so.0
#12 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#17 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#18 gnome_canvas_window_to_world
from /usr/lib64/libgnomecanvas-2.so.0
#19 gnome_canvas_set_scroll_region
from /usr/lib64/libgnomecanvas-2.so.0
#20 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#23 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#24 main
#0 __libc_waitpid
from /lib/libc.so.6

Comment 1 Christian Kirbach 2006-09-01 20:55:17 UTC

Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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