Bug 484227 – crash in Email:

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 484227 - crash in Email:


Summary:	crash in Email:


Status:	RESOLVED DUPLICATE of bug 467763

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-06 19:41 UTC by violerio
Modified:	2007-10-07 10:29 UTC

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

Description violerio 2007-10-06 19:41:24 UTC

Version: 2.10

What were you doing when the application crashed?



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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 210866176 vsize: 210866176 resident: 77901824 share: 51032064 rss: 77901824 rss_rlim: 4294967295
CPU usage: start_time: 1191692680 rtime: 3778 utime: 3594 stime: 184 cutime:27 cstime: 9 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 -1208531232 (LWP 3309)]
[New Thread -1391690864 (LWP 5018)]
[New Thread -1264583792 (LWP 4041)]
[New Thread -1328776304 (LWP 3345)]
[New Thread -1285563504 (LWP 3340)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 168393

Thread 1 (Thread -1208531232 (LWP 3309))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 em_format_set_inline
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#6 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#7 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#8 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 ??
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-2.0.so.0
#13 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /lib/libgobject-2.0.so.0
#18 ??
from /lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#20 g_signal_emit
from /lib/libgobject-2.0.so.0
#21 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /lib/libgobject-2.0.so.0
#26 ??
from /lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#28 g_signal_emit
from /lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#34 ??
from /lib/libglib-2.0.so.0
#35 g_main_loop_run
from /lib/libglib-2.0.so.0
#36 bonobo_main
from /usr/lib/libbonobo-2.so.0
#37 main
#0 __kernel_vsyscall



----------- .xsession-errors (2168 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Max failures exceeded, exiting now
** (gnome-panel:3162): WARNING **: Could not ask power manager to hibernate: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security pol
** Message: <info>  Si è ora connessi alla rete cablata.
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-07 10:29:07 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 467763 ***