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 484703 - evolution crashed with SIGSEGV in pango_layout_line_get_pixel_extents()
evolution crashed with SIGSEGV in pango_layout_line_get_pixel_extents()
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.12.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-08 12:44 UTC by Pedro Villavicencio
Modified: 2009-07-06 16:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Pedro Villavicencio 2007-10-08 12:44:23 UTC 
This bug has been reported here:

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/150472

"Crashed whilst I was away ...."

".

+ Trace 168754

Thread 1 (process 7131)

  • #0 pango_layout_line_get_pixel_extents
    at /build/buildd/pango1.0-1.18.2/pango/pango-layout.c line 4463
  • #1 _do_tooltip
    at e-text.c line 1972
  • #2 g_timeout_dispatch
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 3488
  • #3 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2061
  • #4 g_main_context_iterate
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2694
  • #5 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #6 bonobo_main
    at bonobo-main.c line 311
  • #7 main
    at main.c line 602
  • #8 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #9 _start 






Comment 1


Akhil Laddha





          2009-05-22 07:57:24 UTC
        



Did you get similar crash any time later ?  Can you please try in 2.24.x / 2.26.x and report back, thanks.

it can be a dupe of bug 523463






Comment 2


Akhil Laddha





          2009-07-06 16:27:56 UTC
        



Closing the bug report as no more information has been provided, please feel free to reopen the bug if you can reproduce in 2.26.2 or later, thanks.