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 361521 - crash in Evolution: I have just switched fro...
crash in Evolution: I have just switched fro...
Status: RESOLVED DUPLICATE of bug 359236
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-11 18:40 UTC by Michael Mittler
Modified: 2006-10-12 23:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Michael Mittler 2006-10-11 18:40:31 UTC 
What were you doing when the application crashed?
I have just switched from Trash to Inbox.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 225034240 vsize: 0 resident: 225034240 share: 0 rss: 34242560 rss_rlim: 0
CPU usage: start_time: 1160591885 rtime: 0 utime: 256 stime: 0 cutime:239 cstime: 0 timeout: 17 it_real_value: 0 frequency: 0

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 -1232472400 (LWP 7557)]
[New Thread -1329374304 (LWP 7577)]
[New Thread -1339032672 (LWP 7576)]
[New Thread -1347425376 (LWP 7575)]
[New Thread -1312158816 (LWP 7570)]
[New Thread -1303766112 (LWP 7564)]
[New Thread -1295320160 (LWP 7563)]
[New Thread -1286927456 (LWP 7562)]
[New Thread -1278534752 (LWP 7561)]
[New Thread -1270142048 (LWP 7560)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75869







Comment 1


Karsten Bräckelmann





          2006-10-11 18:49:25 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.







Comment 2


Michael Mittler





          2006-10-12 06:22:36 UTC
        



I've installed debugging symbols as per description but unfortunately I'm not able to reproduce the bug since update from 2.8.1-0ubuntu1 to 2.8.1-0ubuntu2. Sorry!  






Comment 3


Karsten Bräckelmann





          2006-10-12 23:03:23 UTC
        



Thanks for the feedback, Michael. :)

There's absolutely no need to be sorry, that info really is helpful. Just to get this straight, you can not reproduce this since you updated Evo exactly as mentioned in comment 2 -- but you have been able to reproduce this, before that very update?

If so, this is a duplicate of bug 359236. That patch is the only fix Ubuntu backported for that particular update. Marking as such.


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