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 441634 - crash in Evolution: tried to open a jpeg ima...
crash in Evolution: tried to open a jpeg ima...
Status: RESOLVED DUPLICATE of bug 413949
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 441717 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-27 18:06 UTC by mstasiko
Modified: 2007-06-21 03:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mstasiko 2007-05-27 18:06:12 UTC 
What were you doing when the application crashed?
tried to open a jpeg image


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

Memory status: size: 501792768 vsize: 501792768 resident: 68599808 share: 20156416 rss: 88756224 rss_rlim: 1793720320
CPU usage: start_time: 1180289489 rtime: 619 utime: 590 stime: 29 cutime:24 cstime: 6 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 46948580703440 (LWP 12924)]
[New Thread 1107577152 (LWP 12934)]
[New Thread 1107310912 (LWP 12933)]
[New Thread 1090525504 (LWP 12932)]
[New Thread 1098918208 (LWP 12930)]
[New Thread 1082132800 (LWP 12927)]
(no debugging symbols found)
0x00002ab30f042c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 136309

Thread 1 (Thread 46948580703440 (LWP 12924))

  • #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 g_hash_table_lookup
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #4 em_format_set_inline
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #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_button_set_alignment
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #11 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #14 gtk_button_released
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #15 gtk_marshal_BOOLEAN__VOID
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #16 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #17 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #20 gtk_widget_get_default_style
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #21 gtk_propagate_event
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #22 gtk_main_do_event
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #23 gdk_add_client_message_filter
    from /opt/gnome/lib64/libgdk-x11-2.0.so.0
  • #24 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #25 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #27 bonobo_main
    from /opt/gnome/lib64/libbonobo-2.so.0
  • #28 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Pedro Villavicencio





          2007-05-28 12:55:49 UTC
        



*** Bug 441717 has been marked as a duplicate of this bug. ***






Comment 2


palfrey





          2007-05-28 12:55:55 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.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!






Comment 3


Karsten Bräckelmann





          2007-06-21 03:19:27 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 413949 ***