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 356064 - crash in Evolution: just added my google cal...
crash in Evolution: just added my google cal...
Status: RESOLVED DUPLICATE of bug 356065
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-15 04:35 UTC by rsgill
Modified: 2006-09-15 09:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rsgill 2006-09-15 04:35:42 UTC
What were you doing when the application crashed?
just added my google calendar to evolution


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

Memory status: size: 132775936 vsize: 0 resident: 132775936 share: 0 rss: 27295744 rss_rlim: 0
CPU usage: start_time: 1158294814 rtime: 0 utime: 555 stime: 0 cutime:512 cstime: 0 timeout: 43 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 -1232951632 (LWP 20255)]
[New Thread -1308800096 (LWP 20284)]
[New Thread -1300014176 (LWP 20269)]
[New Thread -1291621472 (LWP 20268)]
[New Thread -1260569696 (LWP 20265)]
[New Thread -1251501152 (LWP 20264)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 Karsten Bräckelmann 2006-09-15 09:10:33 UTC
Unfortunately, that stack trace is not very useful in determining the cause of the crash.

However, given the description and the fact you submitted another report just a minute later (bug 356065) that clearly shows adding a webcalendar as well, I assume these are the same crashes.

rsgill, if this assumption if wrong, please feel free to reopen this bug report immediately. Thanks.


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