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 559574 - crash in Evolution Mail and Calendar: i closed application (ev...
crash in Evolution Mail and Calendar: i closed application (ev...
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-11-06 10:41 UTC by yoann.deferi1
Modified: 2008-11-06 23:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description yoann.deferi1 2008-11-06 10:41:32 UTC 
What were you doing when the application crashed?
i closed application (evolution)


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

System: Linux 2.6.27 #1 SMP Mon Oct 13 00:22:24 CEST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 599666688 vsize: 599666688 resident: 49016832 share: 29442048 rss: 49016832 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225967232 rtime: 379 utime: 310 stime: 69 cutime:133 cstime: 26 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f6dade2e700 (LWP 15907)]
0x00007f6da97235ef in waitpid () from /lib/libpthread.so.0

+ Trace 209322

Thread 1 (Thread 0x7f6dade2e700 (LWP 15907))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #6 <signal handler called>
  • #7 ??
  • #8 nsSocketTransportService::Shutdown
    at ../../../dist/include/xpcom/nsCOMPtr.h line 713
  • #9 nsIOService::SetOffline
    at nsIOService.cpp line 617
  • #10 nsIOService::Observe
    at nsIOService.cpp line 774
  • #11 nsObserverList::NotifyObservers
    at nsObserverList.cpp line 128
  • #12 nsObserverService::NotifyObservers
    at nsObserverService.cpp line 181
  • #13 nsXREDirProvider::DoShutdown
    at nsXREDirProvider.cpp line 839
  • #14 XRE_TermEmbedding
    at nsEmbedFunctions.cpp line 159
  • #15 EmbedPrivate::PopStartup
    at EmbedPrivate.cpp line 565
  • #16 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #17 exit
    from /lib/libc.so.6
  • #18 __libc_start_main
    from /lib/libc.so.6
  • #19 _start
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (1288 sec old) ---------------------
** (amule:12405): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (amule:12405): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (amule:12405): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (amule:12405): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (amule:12405): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (amule:12405): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (amule:12405): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2008-11-06 23:08:47 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 541872 ***