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 547591 - crash in Evolution Mail:
crash in Evolution Mail:
Status: RESOLVED DUPLICATE of bug 541872
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-08-13 12:51 UTC by alano.br
Modified: 2008-08-13 12:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description alano.br 2008-08-13 12:51:17 UTC 
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: Tango

Memory status: size: 730656768 vsize: 730656768 resident: 98488320 share: 37548032 rss: 98488320 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218631361 rtime: 3071 utime: 2808 stime: 263 cutime:283 cstime: 42 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f03aee4b790 (LWP 14843)]
[New Thread 0x41aa2950 (LWP 15032)]
[New Thread 0x45b1f950 (LWP 15027)]
[New Thread 0x412a1950 (LWP 14926)]
[New Thread 0x4331a950 (LWP 14925)]
0x00007f03aa7295ff in waitpid () from /lib/libpthread.so.0

+ Trace 205096

Thread 1 (Thread 0x7f03aee4b790 (LWP 14843))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #8 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #9 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #10 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #11 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #12 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #13 XRE_TermEmbedding
    from /usr/lib/xulrunner-1.9/libxul.so
  • #14 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #15 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #16 exit
    from /lib/libc.so.6
  • #17 __libc_start_main
    from /lib/libc.so.6
  • #18 _start
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (8 sec old) ---------------------
feed Melhores do Mundo
feed Pimenteiro
feed Notícias Linux
feed Manual do cafajeste (para mulheres)
feed BR-Linux.org
feed A VIDA SECRETA
feed Under-Linux.Org
feed Jovem Nerd
RSS: cleaning all remaining sessions ...done
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x300004b (Sem títul)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30029a1 (OpenOffice)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30029a1 (OpenOffice)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Kandepu Prasad 2008-08-13 12:53:48 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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