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 542519 - crash in Evolution Mail and Calendar: hello, i have clicked o...
crash in Evolution Mail and Calendar: hello, i have clicked o...
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-07-11 12:38 UTC by GriGric
Modified: 2008-07-26 14:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description GriGric 2008-07-11 12:38:36 UTC
What were you doing when the application crashed?
hello,

i have clicked on the cross on the top of right.

Good day ;)


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Noia

Memory status: size: 531349504 vsize: 531349504 resident: 42942464 share: 27537408 rss: 42942464 rss_rlim: 18446744073709551615
CPU usage: start_time: 1215779853 rtime: 164 utime: 149 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 0x2b6cd2059a80 (LWP 10762)]
(no debugging symbols found)
0x00002b6cc7038edf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b6cd2059a80 (LWP 10762))

  • #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 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #7 NS_ShutdownXPCOM_P
    from /usr/lib/xulrunner-1.9/libxul.so
  • #8 XRE_TermEmbedding
    from /usr/lib/xulrunner-1.9/libxul.so
  • #9 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #10 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #11 exit
    from /lib/libc.so.6
  • #12 __libc_start_main
    from /lib/libc.so.6
  • #13 ??
  • #14 ??
  • #15 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (57468 sec old) ---------------------
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]Invalid and inefficient vfw-avi packed B frames detected
[mpeg4 @ 0x2b974c869bc0]
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-07-14 04:27:25 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.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml, gtk, glib, libsoup, gnome-vfs, libgnome, orbit2 and libgnomeui (as far as those packages are provided by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 André Klapper 2008-07-26 14:00:19 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 ***