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 359810 - crash in Evolution: I was entering the passw...
crash in Evolution: I was entering the passw...
Status: RESOLVED DUPLICATE of bug 359817
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-05 07:21 UTC by alexander.standler
Modified: 2006-10-05 07:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description alexander.standler 2006-10-05 07:21:16 UTC
What were you doing when the application crashed?
I was entering the password for the key ring when evolution crashed


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

Memory status: size: 140722176 vsize: 0 resident: 140722176 share: 0 rss: 25559040 rss_rlim: 0
CPU usage: start_time: 1160032687 rtime: 0 utime: 390 stime: 0 cutime:365 cstime: 0 timeout: 25 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 -1232574800 (LWP 4865)]
[New Thread -1293501536 (LWP 4923)]
[New Thread -1285108832 (LWP 4922)]
[New Thread -1301894240 (LWP 4885)]
[New Thread -1276716128 (LWP 4881)]
[New Thread -1268323424 (LWP 4880)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 André Klapper 2006-10-05 07:22:54 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 André Klapper 2006-10-05 07:58:09 UTC
marking as duplicate of bug 359817 (see bug 359817). thanks for the feedback!

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