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 485069 - crash in Evolution Mail: Just trying to quit (by ...
crash in Evolution Mail: Just trying to quit (by ...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-09 14:44 UTC by Matijs van Zuijlen
Modified: 2009-05-22 11:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Matijs van Zuijlen 2007-10-09 14:44:52 UTC 
What were you doing when the application crashed?
Just trying to quit (by closing the window)


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: gartoon

Memory status: size: 597106688 vsize: 597106688 resident: 44113920 share: 19968000 rss: 44113920 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191941168 rtime: 349 utime: 335 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2ae47f56e550 (LWP 19651)]
[New Thread 0x42003950 (LWP 19667)]
[New Thread 0x43806950 (LWP 19662)]
[New Thread 0x42804950 (LWP 19661)]
[New Thread 0x43005950 (LWP 19660)]
[New Thread 0x41802950 (LWP 19657)]
[New Thread 0x41001950 (LWP 19655)]
[New Thread 0x40800950 (LWP 19654)]
0x00002ae476de2c7f in waitpid () from /lib/libpthread.so.0

+ Trace 169030

Thread 2 (Thread 0x42003950 (LWP 19667))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_mutex_lock_100
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 IA__g_list_find
    at /build/buildd/glib2.0-2.14.1/glib/glist.c line 386
  • #5 folder_changed_change
    at camel-vee-folder.c line 1224
  • #6 session_thread_proxy
    at camel-session.c line 532
  • #7 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.14.1/glib/gthreadpool.c line 265
  • #8 g_thread_create_proxy
    at /build/buildd/glib2.0-2.14.1/glib/gthread.c line 635
  • #9 start_thread
    from /lib/libpthread.so.0
  • #10 clone
    from /lib/libc.so.6
  • #11 ?? 


----------- .xsession-errors (281 sec old) ---------------------
(evolution:19049): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:19049): evolution-mail-WARNING **: couldn't find a vfolder rule in our table? debian-devel-announce mailing list
(evolution:19049): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:19049): evolution-mail-WARNING **: couldn't find a vfolder rule in our table? debian mailing lists
(evolution:19049): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:19049): evolution-mail-WARNING **: couldn't find a vfolder rule in our table? Debian mailing lists
(evolution:19049): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:19049): evolution-mail-WARNING **: couldn't find a vfolder rule in our table? Perl Email Project mailing list
--------------------------------------------------
Comment 1 Akhil Laddha 2009-05-20 06:21:42 UTC 
vfolder code had been rewritten in 2.24.x due to camel db summary changes.

Did you get similar crash any time later ?
Can you please try in 2.24.x / 2.26.x and report back, thanks.
Comment 2 Matijs van Zuijlen 2009-05-22 11:15:45 UTC 
I have not used Evolution in a very long while, having switched to Thunderbird (in its Icedove incarnation). So, I've just done a quick test (open Evolution, update IMAP server location, downloading headers, closing), and Evolution seems to function normally without crashing.

If the code has been completely rewritten, I think it's safe to assume that any crashes that would occur would be quite different from this one.

This bug should therefore probably be marked as resolved.
Comment 3 Akhil Laddha 2009-05-22 11:52:44 UTC 
Thanks for your quick update. After merging kill-bonobo changes in 2.27.x, quiting evolution will be more smooth.