Bug 383392 – Evolution apparently crashing on restarting

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 383392 - Evolution apparently crashing on restarting


Summary:	Evolution apparently crashing on restarting


Status:	RESOLVED DUPLICATE of bug 334966

Product:	evolution
Classification:	Applications
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-07 15:29 UTC by Arthur Hagen
Modified:	2006-12-07 21:37 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Arthur Hagen 2006-12-07 15:28:28 UTC

Distribution: Gentoo Base System version 1.12.6
Package: Evolution
Severity: Normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Gentoo
Synopsis: Evolution apparently crashing on restarting
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.16.1)
Description:
Description of the crash:
The only reason I know it's crashing is that Bug Buddy pops up.

Steps to reproduce the crash:
1. Start Evolution
2. Exit Evolution
3. Start Evolution

Expected Results:
Evolution should start.  Instead Bug Buddy starts

How often does this happen?
Every time Evolution is started "too soon" after exiting Evolution.

Additional Information:
The "so don't do that" rule doesn't work well, because of another bug
with Evolution, where it won't show new NNTP-retrieved messages unless
Evolution is closed and then started again.  The only viable workaround
is to wait (longer for slower machines)


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208272240 (LWP 10862)]
[New Thread -1286243424 (LWP 10961)]
[New Thread -1287046240 (LWP 10960)]
[New Thread -1277330528 (LWP 10883)]
[New Thread -1268937824 (LWP 10881)]
[New Thread -1247724640 (LWP 10878)]
[New Thread -1238537312 (LWP 10874)]
[New Thread -1230111840 (LWP 10873)]
[New Thread -1221719136 (LWP 10872)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 92326

Thread 1 (Thread -1208272240 (LWP 10862))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 e_shell_window_set_title
#6 e_shell_window_set_title
#7 _ORBIT_skel_small_GNOME_Evolution_ShellView_setTitle
from /usr/lib/evolution/2.6/libeshell.so.0
#8 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#9 GNOME_Evolution_ShellView_setTitle
from /usr/lib/evolution/2.6/libeshell.so.0
#10 e_component_view_set_title
from /usr/lib/evolution/2.6/libeshell.so.0
#11 ??
#12 ??
from /usr/lib/evolution/2.6/components/libevolution-mail.so
#13 ??
#14 ??
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2006-12-07 15:29 -------

Comment 1 André Klapper 2006-12-07 21:37:28 UTC

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 334966 ***