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 546858 - 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-07 20:29 UTC by alano.br
Modified: 2008-08-10 21:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description alano.br 2008-08-07 20:29:22 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: 740143104 vsize: 740143104 resident: 71184384 share: 32669696 rss: 71184384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218118377 rtime: 9132 utime: 7998 stime: 1134 cutime:3415 cstime: 368 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fd124354790 (LWP 3711)]
[New Thread 0x437d6950 (LWP 10443)]
[New Thread 0x43fd7950 (LWP 10438)]
[New Thread 0x410fb950 (LWP 3812)]
[New Thread 0x40838950 (LWP 3811)]
0x00007fd11fc33edf in waitpid () from /lib/libpthread.so.0

+ Trace 204823

Thread 1 (Thread 0x7fd124354790 (LWP 3711))

  • #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 (20907 sec old) ---------------------
	->lsb/usr/postscript/Savin/Savin-2404WD_PS.ppd.gz (Savin 2404WD PS[0]) and
	->lsb/usr/foomatic-rip/openprinting-gs-builtin/Savin/Savin-2404WD-Postscript.ppd.gz (Savin 2404WD PS)[0]

** (gnome-cups-add:5693): WARNING **: Two ppds have driver == 'Padrão'
	->lsb/usr/postscript/Savin/Savin-2522_PXL.ppd.gz (Savin 2522 PXL[0]) and
	->lsb/usr/foomatic-rip/openprinting-gs-builtin/Savin/Savin-2522-pxlmono.ppd.gz (Savin 2522 PXL)[0]

** (gnome-cups-add:5693): WARNING **: Two ppds have driver == 'Padrão'
	->lsb/usr/postscript/Savin/Savin-2527_PXL.ppd.gz (Savin 2527 PXL[0]) and
	->lsb/usr/foomatic-rip/openprinting-gs-builtin/Savin/Savin-2527-pxlmono.ppd.gz (Savin 2527 PXL)[0]

** (gnome-cups-add:5693): WARNING **: Two ppds have driver == 'Padrão'
	->lsb/usr/postscript/Savin/Savin-2535_2235_PS.ppd.gz (Savin 2535/2235 PS[0]) and
	->lsb/usr/foomatic-rip/openprinting-gs-builtin/Savin/Savin-2535_2235-Postscript.ppd.gz (Savin 253
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Johnny Jacob 2008-08-08 00:18:59 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2008-08-10 21:28:53 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 ***