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 357659 - crash in Evolution: typed the users name in ...
crash in Evolution: typed the users name in ...
Status: RESOLVED DUPLICATE of bug 357082
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-25 18:32 UTC by Wendell MacKenzie
Modified: 2006-09-25 20:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Wendell MacKenzie 2006-09-25 18:32:21 UTC 
What were you doing when the application crashed?
typed the users name in the To: field again... :(


Distribution: SUSE LINUX 10.1 (i586)
Gnome Release: 2.16.0 2006-09-12 (GARNOME)
BugBuddy Version: 2.16.0

Memory status: size: 218066944 vsize: 0 resident: 218066944 share: 0 rss: 71843840 rss_rlim: 0
CPU usage: start_time: 1159203163 rtime: 0 utime: 6163 stime: 0 cutime:5866 cstime: 0 timeout: 297 it_real_value: 0 frequency: 0

Backtrace was generated from '/home/wendell/garnome/bin/evolution-2.8'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233140048 (LWP 5509)]
[New Thread -1337779296 (LWP 5622)]
[New Thread -1333806176 (LWP 5541)]
[New Thread -1325413472 (LWP 5539)]
[New Thread -1315947616 (LWP 5536)]
[New Thread -1306362976 (LWP 5533)]
[New Thread -1297970272 (LWP 5532)]
[New Thread -1289577568 (LWP 5529)]
[New Thread -1277170784 (LWP 5527)]
[New Thread -1268778080 (LWP 5526)]
[New Thread -1250329696 (LWP 5525)]
[New Thread -1259115616 (LWP 5524)]
[New Thread -1240208480 (LWP 5522)]
0xb7f4b410 in ?? ()

+ Trace 73228







Comment 1


Karsten Bräckelmann





          2006-09-25 20:00:47 UTC
        



So this would be bug 357082... ;-)


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