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 467234 - crash in Evolution: Ich habe eine Email umle...
crash in Evolution: Ich habe eine Email umle...
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-16 07:41 UTC by norbert.appions
Modified: 2007-10-19 01:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description norbert.appions 2007-08-16 07:41:25 UTC 
What were you doing when the application crashed?
Ich habe eine Email umleiten wollen, die einen Anhang hatte. Dann konnte ich den Text nicht mehr editieren. Dann versuchte ich von "Vorformatiert" auf "Normal" umzuschalten - Absturz


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 725266432 vsize: 725266432 resident: 32591872 share: 34209792 rss: 66801664 rss_rlim: 1793720320
CPU usage: start_time: 1187246905 rtime: 3100 utime: 2716 stime: 384 cutime:53 cstime: 37 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47260389805264 (LWP 5070)]
[New Thread 1115969856 (LWP 5609)]
[New Thread 1107577152 (LWP 5110)]
[New Thread 1107310912 (LWP 5109)]
[New Thread 1098918208 (LWP 5108)]
[New Thread 1090525504 (LWP 5107)]
[New Thread 1082132800 (LWP 5083)]
(no debugging symbols found)
0x00002afba8497c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 155602

Thread 1 (Thread 47260389805264 (LWP 5070))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 html_engine_set_clueflow_style
    from /opt/gnome/lib64/libgtkhtml-3.8.so.15
  • #4 gtk_html_set_paragraph_style
    from /opt/gnome/lib64/libgtkhtml-3.8.so.15
  • #5 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #6 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #9 gtk_widget_activate
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #10 gtk_menu_shell_activate_item
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #11 gtk_menu_shell_append
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #12 gtk_marshal_BOOLEAN__VOID
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #13 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #14 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #17 gtk_widget_get_default_style
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #18 gtk_propagate_event
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #19 gtk_main_do_event
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #20 gdk_add_client_message_filter
    from /opt/gnome/lib64/libgdk-x11-2.0.so.0
  • #21 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #22 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #24 bonobo_main
    from /opt/gnome/lib64/libbonobo-2.so.0
  • #25 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


André Klapper





          2007-08-18 11:45:29 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, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome 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





          2007-10-19 01:24:38 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!