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 545416 - 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-07-30 01:14 UTC by alano.br
Modified: 2008-07-30 05:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description alano.br 2008-07-30 01:14:19 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: SphereCrystal
Icon Theme: Noia

Memory status: size: 706699264 vsize: 706699264 resident: 66650112 share: 30560256 rss: 66650112 rss_rlim: 18446744073709551615
CPU usage: start_time: 1217375540 rtime: 4470 utime: 3918 stime: 552 cutime:271 cstime: 83 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f6ca5d857a0 (LWP 3724)]
0x00007f6ca1666edf in waitpid () from /lib/libpthread.so.0

+ Trace 204134

Thread 1 (Thread 0x7f6ca5d857a0 (LWP 3724))

  • #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 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #5 <signal handler called>
  • #6 ??
  • #7 nsSocketTransportService::Shutdown
    at ../../../dist/include/xpcom/nsCOMPtr.h line 713
  • #8 nsIOService::SetOffline
    at nsIOService.cpp line 617
  • #9 nsIOService::Observe
    at nsIOService.cpp line 774
  • #10 nsObserverList::NotifyObservers
    at nsObserverList.cpp line 128
  • #11 nsObserverService::NotifyObservers
    at nsObserverService.cpp line 181
  • #12 nsXREDirProvider::DoShutdown
    at nsXREDirProvider.cpp line 839
  • #13 XRE_TermEmbedding
    at nsEmbedFunctions.cpp line 159
  • #14 EmbedPrivate::PopStartup
    at EmbedPrivate.cpp line 565
  • #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 (42 sec old) ---------------------
(npviewer.bin:6581): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
(npviewer.bin:6581): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(npviewer.bin:6581): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
Network timeout occured. Cancel active operations.
RSS: cleaning all remaining sessions ...done

(gnome-terminal:6795): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

(gnome-terminal:6823): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Aviso do gerenciador de janelas: last_user_time (474986112) is greater than comparison timestamp (4960290).  This most likely represents a buggy client sending inaccurate timestamps in messages such a
Aviso do gerenciador de janelas: 0x3600020 (Terminal) appears to be one of the offending windows with a timestamp of 474986112.  Working around...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-07-30 05:26:14 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 ***