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 592852 - crash in Evolution Mail and Calendar: I had opened an attached...
crash in Evolution Mail and Calendar: I had opened an attached...
Status: RESOLVED DUPLICATE of bug 344076
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.26.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-08-24 05:48 UTC by jan.teichmann
Modified: 2009-08-24 14:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description jan.teichmann 2009-08-24 05:48:03 UTC
What were you doing when the application crashed?
I had opened an attached text document



Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc)
BugBuddy Version: 2.26.0

System: Linux 2.6.29.6-217.2.8.fc11.x86_64 #1 SMP Sat Aug 15 01:06:26 EDT 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad

Memory status: size: 1733857280 vsize: 1733857280 resident: 51871744 share: 24449024 rss: 51871744 rss_rlim: 18446744073709551615
CPU usage: start_time: 1251092665 rtime: 313 utime: 263 stime: 50 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f5d84dfa910 (LWP 20066)]
[New Thread 0x7f5d857fb910 (LWP 20043)]
[New Thread 0x7f5d861fc910 (LWP 20042)]
[New Thread 0x7f5d875fe910 (LWP 20039)]
[New Thread 0x7f5d87fff910 (LWP 20038)]
[New Thread 0x7f5da0d25910 (LWP 20037)]
[New Thread 0x7f5da1726910 (LWP 20036)]
[New Thread 0x7f5da2127910 (LWP 20035)]
[New Thread 0x7f5da2b28910 (LWP 20034)]
[New Thread 0x7f5da3fff910 (LWP 20033)]
[New Thread 0x7f5db8bef910 (LWP 20031)]
[New Thread 0x7f5dbbfff910 (LWP 20026)]
[New Thread 0x7f5dc0d7f910 (LWP 20025)]
0x0000003c7540ea2d in __libc_waitpid (pid=20127, 
    stat_loc=<value optimized out>, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
Current language:  auto; currently minimal

Thread 1 (Thread 0x7f5dcbac17f0 (LWP 20017))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #6 *__GI_abort
    at abort.c line 88
  • #7 IA__g_assertion_message
  • #8 IA__g_assertion_message_expr
    at gtestutils.c line 1312
  • #9 gtk_layout_move_internal
    at gtklayout.c line 394
  • #10 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #11 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #12 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #13 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #14 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #15 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #16 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #17 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #18 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #19 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #20 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #21 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #22 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #23 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #24 IA__g_closure_invoke
    at gclosure.c line 767
  • #25 signal_emit_unlocked_R
    at gsignal.c line 3285
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2990
  • #27 IA__g_signal_emit
    at gsignal.c line 3037
  • #28 gtk_widget_event_internal
    at gtkwidget.c line 4764
  • #29 IA__gtk_main_do_event
    at gtkmain.c line 1558
  • #30 gdk_window_process_updates_internal
    at gdkwindow.c line 2611
  • #31 IA__gdk_window_process_all_updates
    at gdkwindow.c line 2677
  • #32 gtk_container_idle_sizer
    at gtkcontainer.c line 1353
  • #33 gdk_threads_dispatch
    at gdk.c line 498
  • #34 g_main_dispatch
    at gmain.c line 1824
  • #35 IA__g_main_context_dispatch
    at gmain.c line 2377
  • #36 g_main_context_iterate
    at gmain.c line 2455
  • #37 IA__g_main_loop_run
    at gmain.c line 2663
  • #38 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #39 main
    at main.c line 704


----------- .xsession-errors (6 sec old) ---------------------
Fenstermanager-Warnung:Gespeicherte Sitzungsdatei /home/jan/.config/metacity/sessions/1026822372f8e35110125106645285395100000191370024.ms konnte nicht gelesen werden: Datei »/home/jan/.config/metacit
Initializing nautilus-gdu extension
** (nautilus:19226): WARNING **: Unable to add monitor: Nicht unterstützt
(npviewer.bin:19582): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
(npviewer.bin:19582): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
gnome-session[19137]: WARNING: Could not ask power manager to suspend: Message did not receive a reply (timeout by message bus)
** (evolution:20017): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:20017): DEBUG: mailto URL program: evolution
**
Gtk:ERROR:gtklayout.c:394:gtk_layout_move_internal: assertion failed: (child)
Missing separate debuginfo for /usr/lib64/libtdb.so.1
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/56/1175f4b142f66a751e5f31b5f5726780123787.debug
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-08-24 14:14:39 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 bug 344076 ***