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 572485 - crash in Evolution Mail and Calendar:
crash in Evolution Mail and Calendar:
Status: RESOLVED DUPLICATE of bug 561332
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: 2009-02-19 20:28 UTC by jsmith
Modified: 2009-02-20 03:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description jsmith 2009-02-19 20:28:25 UTC
What were you doing when the application crashed?



Distribution: openSUSE 11.0 (i586)
Gnome Release: 2.22.1 2008-06-07 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.20-0.1-pae #1 SMP 2008-12-12 20:30:38 +0100 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Gilouche

Memory status: size: 57397248 vsize: 57397248 resident: 5713920 share: 10256384 rss: 15970304 rss_rlim: 1805035520
CPU usage: start_time: 1235075269 rtime: 61 utime: 49 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/evolution-exchange-storage'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb6318b80 (LWP 6489)]
[New Thread 0xb54ffb90 (LWP 6544)]
[New Thread 0xb5f22b90 (LWP 6491)]
0xffffe430 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6318b80 (LWP 6489))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #10 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #11 message_removed
  • #12 sync_deletions
  • #13 connection_handler
  • #14 g_io_unix_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (488 sec old) ---------------------
Window manager warning: Property _NET_WM_ICON_NAME on window 0x3c0790a contained invalid UTF-8
(gnome-panel:3296): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
(gnome-panel:3296): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
Window manager warning: Property _NET_WM_NAME on window 0x3c07faa contained invalid UTF-8
Window manager warning: Property _NET_WM_ICON_NAME on window 0x3c07faa contained invalid UTF-8
(gnome-panel:3296): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
(gnome-panel:3296): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
--------------------------------------------------
Comment 1 Akhil Laddha 2009-02-20 03:44:07 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 561332 ***