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 364236 - crash in pango_layout_get_cursor_pos
crash in pango_layout_get_cursor_pos
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Milan Crha
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-22 18:06 UTC by crash
Modified: 2010-07-02 01:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
the calender file (47.62 KB, text/calendar)
2007-01-16 08:55 UTC, crash
Details
valid vCalendar causes crash too (885 bytes, text/directory)
2007-08-13 10:45 UTC, Milan Crha
Details

Description crash 2006-10-22 18:06:33 UTC
What were you doing when the application crashed?
I imported a file in vCal format and succeeded. The appointments are in swedish and apparantly there was some utf versus iso issue because all the special swedish letters (äåö) were replaced with '?' . Right after changing one of the questionmarks to ä Evolution crashed.

I can reproduce the bug by doing as described above.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 233512960 vsize: 0 resident: 233512960 share: 0 rss: 35495936 rss_rlim: 0
CPU usage: start_time: 1161539985 rtime: 0 utime: 611 stime: 0 cutime:577 cstime: 0 timeout: 34 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233025360 (LWP 8437)]
[New Thread -1364915296 (LWP 8469)]
[New Thread -1353417824 (LWP 8458)]
[New Thread -1303565408 (LWP 8457)]
[New Thread -1295172704 (LWP 8454)]
[New Thread -1311994976 (LWP 8450)]
[New Thread -1286780000 (LWP 8445)]
[New Thread -1278387296 (LWP 8444)]
[New Thread -1269994592 (LWP 8443)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233025360 (LWP 8437))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 pango_layout_get_cursor_pos
    from /usr/lib/libpango-1.0.so.0
  • #11 e_text_draw
    at e-text.c line 1635
  • #12 gnome_canvas_root
    from /usr/lib/libgnomecanvas-2.so.0
  • #13 gnome_canvas_item_new
    from /usr/lib/libgnomecanvas-2.so.0
  • #14 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gnome_canvas_window_to_world
    from /usr/lib/libgnomecanvas-2.so.0
  • #22 gnome_canvas_set_scroll_region
    from /usr/lib/libgnomecanvas-2.so.0
  • #23 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #27 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #28 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 1 Kjartan Maraas 2007-01-15 22:36:18 UTC
Can you still reproduce this problem or has it been fixed since? Any chance you have the calendar file available somewhere?
Comment 2 crash 2007-01-16 08:55:37 UTC
Created attachment 80368 [details]
the calender file
Comment 3 crash 2007-01-16 08:56:55 UTC
Comment on attachment 80368 [details]
the calender file

Yes, the bug can still be reproduced.
Comment 4 Milan Crha 2007-08-13 10:45:29 UTC
Created attachment 93565 [details]
valid vCalendar causes crash too

This is a vCalendar file with only 3 events on 13.8.2007 with no utf-8 invalid character at all. The problem here is in pango, when I enter event in day_view (the cursor will be blinking on a screen - not edit dialog), then when I go from longer line to shorter line with arrow-up key and staying at line-index bigger than the destination line has characters, then the pango cause crash with message:
-----
Pango-ERROR **: file pango-layout.c: line 2061 (pango_layout_line_get_char_direction): should not be reached
aborting...
-----
Pango could not evaluate char direction in these cases, somehow. When I move between lines at the beginning of lines, then it will not crash.

Do we move this bug to pango?
Comment 5 Behdad Esfahbod 2007-08-21 02:23:06 UTC
Tried importing it in my evo.  Doesn't do anything.
Comment 6 Milan Crha 2007-08-21 07:14:37 UTC
How do you do that? It works for me just fine. I did:
a) File->Import, choose "Import single file", browse for file
b) the combo will show "vCalendar files (.vcf)"
c) choose "Appointments and meetings" and maybe "On This Computer/Personal"
d) forward, import
e) be sure On This Computer/Personal is checked in source list

you should see at 9:00-11:00 an event with summary:
TIF010

Fysiken omkring oss

Frel

f3aamp

TKTFY-1

and moving cursor from the end of the longest line (the second one) up or down will cause crash in pango.
It's very strange, but when I paste the text from this report into the summary field, then it works just fine, but with the imported event it isn't. I see there only one difference, the imported event uses '\r\n' but the pasted one only "\n" as new line markers, so it seems the '\r' makes trouble here, maybe.
Comment 7 André Klapper 2010-05-20 20:32:55 UTC
NEEDINFO as per last comment.
Comment 8 Akhil Laddha 2010-07-02 01:51:15 UTC
Please feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.30.2 or later, thanks.