GNOME Bugzilla – Bug 359945
No SMTP server given crashes Evo on Send and Receive
Last modified: 2010-05-20 20:32:33 UTC
What were you doing when the application crashed? I get this crash everytime I press Send / Recieve. Most annoying. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 321191936 vsize: 321191936 resident: 77787136 share: 20312064 rss: 77787136 rss_rlim: -1 CPU usage: start_time: 1160066142 rtime: 1162 utime: 1029 stime: 133 cutime:25 cstime: 22 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46976948161808 (LWP 18581)] [New Thread 1115969872 (LWP 18704)] [New Thread 1115703632 (LWP 18593)] [New Thread 1107310928 (LWP 18590)] [New Thread 1098918224 (LWP 18589)] [New Thread 1090525520 (LWP 18586)] [New Thread 1082132816 (LWP 18583)] 0x00002ab9a802b6df in __libc_waitpid () from /lib/libc.so.6
+ Trace 74730
Thread 7 (Thread 1082132816 (LWP 18583))
Thread 6 (Thread 1090525520 (LWP 18586))
Thread 5 (Thread 1098918224 (LWP 18589))
Thread 4 (Thread 1107310928 (LWP 18590))
Thread 3 (Thread 1115703632 (LWP 18593))
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.
Program received signal SIGSEGV, Segmentation fault.
+ Trace 74744
Thread 46991833935120 (LWP 19570)
I hope that's enough info :-).
I just saw I forgot "thread apply all". Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47225007971600 (LWP 20058)] format_url (internal_url=<value optimized out>, account_name=0x0) at mail-send-recv.c:274 274 mail-send-recv.c: No such file or directory. in mail-send-recv.c (gdb) thread apply all bt
+ Trace 74745
Thread 8 (Thread 1115703632 (LWP 20118))
Thread 7 (Thread 1107310928 (LWP 20111))
Thread 6 (Thread 1098918224 (LWP 20082))
Thread 4 (Thread 1090525520 (LWP 20078))
Thread 1 (Thread 47225007971600 (LWP 20058))
I just found out what caused this bug. I had no SMTP-server set for some unknown reason. It could have just telled me instead of crashing though :-P.
Uhm -- *no* SMTP server at all? Not even some random, possibly white-space only string? How have you been able to finish the wizard? Anyway, thanks for the response and these great details, Christian. :) Adjusting summary.
No, it was completely empty, including the auth-info, TLS etc... I have no idea how they disappered since I haven't touched those settings in a _long_ time :-).
Whoops, correcting Summary. Hmm, complete empty should not even be possible, without manually editing the GConf stored settings. This one is up for the developers.
I don't get any crash in 2.28.1 or 2.29.2 while doing send/receive without smtp server.
Closing as OBSOLETE. If this still happens in a recent version please leave a comment.