Bug 718424

Summary: Crash when using the collaboration plugin
Product: [Fedora] Fedora Reporter: Elad Alfassa <elad>
Component: libinfinityAssignee: Till Maas <opensource>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: fedora, icq, opensource
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 17:54:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
backtrace none

Description Elad Alfassa 2011-07-02 19:14:09 UTC
Description of problem:
[elad@elephant ~]$ gedit 

(gedit:1551): Gtk-CRITICAL **: gtk_list_store_set_column_types: assertion `priv->columns_dirty == 0' failed
**
ERROR:inf-text-gtk-view.c:930:inf_text_gtk_view_draw_after_cb: assertion failed: (area_end >= area_begin)
Aborted (core dumped)


Version-Release number of selected component (if applicable):
gedit-3.0.6-1.fc15.x86_64
gedit-collaboration-3.0.0-1.fc15.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Open a file created by another user
2.Try to write something
3.Crash


Additional info:

ABRT didn't liked the dump so it removed it, 
    Jul 2 22:07:11 elephant abrt[1656]: Unrecognized variable 'DumpLocation' in '/etc/abrt/abrt.conf'
    Jul 2 22:07:11 elephant abrtd: Unrecognized variable 'DumpLocation' in '/etc/abrt/abrt.conf'
    Jul 2 22:07:12 elephant abrt[1656]: saved core dump of pid 1624 (/usr/bin/gedit) to /var/spool/abrt/ccpp-2011-07-02-22:07:11-1624.new/coredump (77766656 bytes)
    Jul 2 22:07:12 elephant abrtd: Unrecognized variable 'DumpLocation' in '/etc/abrt/abrt.conf'
    Jul 2 22:07:12 elephant abrtd: Directory 'ccpp-2011-07-02-22:07:11-1624' creation detected
    Jul 2 22:07:12 elephant abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2011-07-02-22:07:11-1624 (res:2), deleting

I'll try to get a backtrace as soon as I can.

Comment 1 Elad Alfassa 2011-07-03 06:23:10 UTC
Created attachment 511026 [details]
backtrace

Backtrace

Comment 2 Elad Alfassa 2011-07-03 06:48:16 UTC
This seems to be the cause for the crash:
#2  0x00000039bc0665bd in g_assertion_message (domain=<optimized out>, 
    file=<optimized out>, line=<optimized out>, func=
    0x7fffea7b8d80 "inf_text_gtk_view_draw_after_cb", message=
    0x1c17c40 "assertion failed: (area_end >= area_begin)")
    at gtestutils.c:1358


I did some more debugging and found out that it only happens if I write RTL characters, such as Hebrew א.
Which means that the code that colors the lines doesn't support RTL.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Elad Alfassa 2011-07-03 08:10:10 UTC
Writing ABCDא will not cause a crash, but if the line starts with an RTL character, it would crash.




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Ignacio Casal Quinteiro (nacho) 2011-07-03 08:59:36 UTC
Reading the bt seems like a bug in libinfinity

Comment 5 Elad Alfassa 2011-07-03 09:02:30 UTC
Changing component to libinfinity.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Till Maas 2012-07-08 22:05:35 UTC
Can this be reproduced in Fedora 16 or 17?

Comment 7 Elad Alfassa 2012-07-09 10:35:01 UTC
Indeed. It seems to be caused by the highlighting code not taking the possibility the line might start in the right side of the screen into account when trying to highlight the text.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 8 Till Maas 2012-07-10 06:53:30 UTC
There will be an updated version in updates-testing soon, can you please try to reproduce the bug with it?
https://admin.fedoraproject.org/updates/libinfinity-0.5.2-1.fc17

Comment 9 Till Maas 2012-09-05 09:08:19 UTC
Since there was no reply in nearly two months, I close this bug.

Comment 10 Elad Alfassa 2012-09-05 09:17:06 UTC
Sorry, this got lost among hundreds of other emails, or maybe I never got it. I tested it now, and it seems to still crash. Please reopen this bug.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 11 Till Maas 2013-01-22 19:13:10 UTC
There is another update, would you please test it?
https://admin.fedoraproject.org/updates/FEDORA-2013-0729/libinfinity-0.5.3-1.fc17

Comment 12 Fedora End Of Life 2013-07-04 06:22:52 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2013-08-01 17:55:03 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.