Bug 440296 – crash in Evolution: I restored the applicati...

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 440296 - crash in Evolution: I restored the applicati...


Summary:	crash in Evolution: I restored the applicati...


Status:	RESOLVED DUPLICATE of bug 330728

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.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-21 22:07 UTC by javinovich
Modified:	2007-05-23 16:06 UTC

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

Description javinovich 2007-05-21 22:07:38 UTC

What were you doing when the application crashed?
I restored the application after switching desktops, then I clicked on the mail button (I was using the contacts view) it showed the mail view and after that the application crashed.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 616517632 vsize: 616517632 resident: 19832832 share: 20865024 rss: 40697856 rss_rlim: 1785364480
CPU usage: start_time: 1179762311 rtime: 3124 utime: 2780 stime: 344 cutime:40 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47041055710384 (LWP 6736)]
[New Thread 1115969856 (LWP 7267)]
[New Thread 1107577152 (LWP 6770)]
[New Thread 1107310912 (LWP 6769)]
[New Thread 1098918208 (LWP 6768)]
[New Thread 1090525504 (LWP 6747)]
[New Thread 1082132800 (LWP 6744)]
0x00002ac896f4cc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 135413

Thread 1 (Thread 47041055710384 (LWP 6736))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ect_check
from /opt/gnome/lib64/evolution/2.8/libevolution-a11y.so.0
#4 ect_get_name
from /opt/gnome/lib64/evolution/2.8/libevolution-a11y.so.0
#5 gnome_accessibility_module_shutdown
from /opt/gnome/lib64/gtk-2.0/modules/libatk-bridge.so
#6 gnome_accessibility_module_shutdown
from /opt/gnome/lib64/gtk-2.0/modules/libatk-bridge.so
#7 gnome_accessibility_module_shutdown
from /opt/gnome/lib64/gtk-2.0/modules/libatk-bridge.so
#8 atk_focus_tracker_notify
from /opt/gnome/lib64/libatk-1.0.so.0
#9 gnome_accessibility_module_init
from /opt/gnome/lib64/gtk-2.0/modules/libgail.so
#10 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#11 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#12 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#13 bonobo_main
from /opt/gnome/lib64/libbonobo-2.so.0
#14 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 palfrey 2007-05-21 23:23:50 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 javinovich 2007-05-23 16:00:04 UTC

I'm using GNOME as provided by http://software.opensuse.org/download/GNOME:/STABLE/openSUSE_10.2/x86_64/ not the original set that came with the downloaded DVD.

I still doesn't have luck finding the debuginfo packages although I know without that it wouldn't be helpful the report.

Comment 3 palfrey 2007-05-23 16:06:21 UTC

We've managed to find out that this particular bug has already been reported into our bug tracking system, so we won't need the debuginfo after all. Please feel free to report any further bugs you find.


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