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 358262 - crash in Evolution: Quitting.
crash in Evolution: Quitting.
Status: RESOLVED DUPLICATE of bug 358330
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
: 358274 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-29 09:54 UTC by Fergal Daly
Modified: 2006-09-29 16:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
stack trace (7.20 KB, text/plain)
2006-09-29 13:03 UTC, Fergal Daly
Details

Description Fergal Daly 2006-09-29 09:54:39 UTC
What were you doing when the application crashed?
Quitting.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 436400128 vsize: 0 resident: 436400128 share: 0 rss: 337453056 rss_rlim: 0
CPU usage: start_time: 1159522154 rtime: 0 utime: 20664 stime: 0 cutime:19267 cstime: 0 timeout: 1397 it_real_value: 0 frequency: 5

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232558416 (LWP 11507)]
[New Thread -1306928224 (LWP 11558)]
[New Thread -1298535520 (LWP 11557)]
[New Thread -1289749600 (LWP 11530)]
[New Thread -1279288416 (LWP 11528)]
[New Thread -1270502496 (LWP 11526)]
[New Thread -1262072928 (LWP 11524)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 Karsten Bräckelmann 2006-09-29 11:53:30 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Does this happen always?
Comment 2 Karsten Bräckelmann 2006-09-29 11:57:31 UTC
*** Bug 358274 has been marked as a duplicate of this bug. ***
Comment 3 Fergal Daly 2006-09-29 13:03:23 UTC
Created attachment 73629 [details]
stack trace
Comment 4 Fergal Daly 2006-09-29 13:04:12 UTC
It always happens and it happened with 2.6 too. I think since upgrading to 2.6 > 6 months ago, it has cleanly exited twice. Sorry for not filing a bug earlier.

Symbolised trace attached. Let me know if you need me to install any other -dbg packages.
Comment 5 Karsten Bräckelmann 2006-09-29 15:28:50 UTC
Thanks for the fast response and the additional details, Fergal. :)

From the stacktrace, I can see you got debugging packages installed at least for glib and e-d-s. However, the stacktrace still looks a bit odd to me. :/

In case you don't already, can you please install debugging packages for evolution and a few more basic GNOME libs as well? More details can be found here:
  http://live.gnome.org/GettingTraces/DistroSpecificInstructions


NEEDINFO. If all those debugging packages actually have been installed already, please simply reopen this report. Thanks.
Comment 6 Fergal Daly 2006-09-29 15:58:35 UTC
I did install them. evo, e-d-s, libglib2.0.0, libgtk2.0 and some other stuff mentioned on tha page.

Oddly, I got a stack trace a before I install e-d-s-ebg and I saw some unsymbolised things referring to it so I installed it and got another stack trace but it seemed a lot shorted than. Maybe something odd with bug-buddy.

I get another.
Comment 7 Fergal Daly 2006-09-29 15:59:39 UTC
rather than cut and paste, I let bug buddy create another new bug.

http://bugzilla.gnome.org/show_bug.cgi?id=358330
Comment 8 Karsten Bräckelmann 2006-09-29 16:41:59 UTC

*** This bug has been marked as a duplicate of 358330 ***
Comment 9 Karsten Bräckelmann 2006-09-29 16:46:39 UTC
Great, thanks for all your effort, Fergal. :)

The last stacktrace in bug 358330 is good and got all the previously missing function calls and debugging symbols. Obviously a duplicate, as Andre already marked.