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 573048 - crash in Evolution Mail and Calendar: Right-clicking on a grou...
crash in Evolution Mail and Calendar: Right-clicking on a grou...
Status: RESOLVED DUPLICATE of bug 569700
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-02-25 00:41 UTC by Aron Hsiao
Modified: 2009-02-25 03:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Aron Hsiao 2009-02-25 00:41:44 UTC 
What were you doing when the application crashed?
Right-clicking on a group of highlighted messages in the message index.


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.15 #3 PREEMPT Wed Feb 11 06:17:37 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Shiki-Human
Icon Theme: gnome-brave

Memory status: size: 184180736 vsize: 184180736 resident: 43802624 share: 22274048 rss: 43802624 rss_rlim: 18446744073709551615
CPU usage: start_time: 1235522370 rtime: 723 utime: 685 stime: 38 cutime:2 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb803a980 (LWP 4394)]
[New Thread 0xb55f9b90 (LWP 4640)]
[New Thread 0xb6e2bb90 (LWP 4439)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 212870

Thread 2 (Thread 0xb55f9b90 (LWP 4640))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S line 136
  • #2 _L_lock_89
    from /lib/libpthread.so.0
  • #3 __pthread_mutex_lock
    at pthread_mutex_lock.c line 86
  • #4 segv_redirect
    at main.c line 423
  • #5 <signal handler called>
  • #6 camel_mime_parser_read
    at camel-mime-parser.c line 655
  • #7 stream_read
    at camel-http-stream.c line 487
  • #8 camel_stream_read
    at camel-stream.c line 98
  • #9 emfh_gethttp
    at em-format-html.c line 525
  • #10 efh_format_exec
    at em-format-html.c line 1299
  • #11 mail_msg_proxy
    at mail-mt.c line 520
  • #12 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #13 g_thread_create_proxy
    at gthread.c line 635
  • #14 start_thread
    at pthread_create.c line 297
  • #15 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130 


----------- .xsession-errors (105 sec old) ---------------------
(gnome-panel:4021): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x812d858
(gnome-panel:4021): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x812d858
** (nautilus:3892): WARNING **: Unable to add monitor: Not supported
Throttle level is 5
Unable to open desktop file nautilus-home.desktop for panel launcher
Unable to open desktop file nautilus-home.desktop for panel launcher
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4162): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4162): DEBUG: mailto URL program: evolution
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4394): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4394): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Akhil Laddha 2009-02-25 03:42:54 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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