RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1255831 - [abrt] Crash under html_text_get_link_at_offset()
Summary: [abrt] Crash under html_text_get_link_at_offset()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gtkhtml3
Version: 7.2
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard: abrt_hash:1ffe0bd8228dda9929b1f5901d7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-21 16:23 UTC by Jiri Koten
Modified: 2015-11-19 07:59 UTC (History)
3 users (show)

Fixed In Version: gtkhtml3-4.8.5-2.el7
Doc Type: Bug Fix
Doc Text:
Cause: crash could happen when a link insert was initiated in the HTML message format Consequence: inserting an image and right after that a link could cause a crash due to no object type checking and casting an object into a type it was not, thus accessing object structure members with incorrect values. Fix: proper type checking had been added Result: application doesn't crash when a link is inserted right after inserting an image
Clone Of:
Environment:
Last Closed: 2015-11-19 07:59:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: backtrace (49.47 KB, text/plain)
2015-08-21 16:28 UTC, Jiri Koten
no flags Details
patch to fix the crash (2.48 KB, patch)
2015-08-26 11:40 UTC, Milan Crha
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 701247 0 None None None Never
Red Hat Product Errata RHBA-2015:2226 0 normal SHIPPED_LIVE evolution bug fix and enhancement update 2015-11-19 08:37:43 UTC

Description Jiri Koten 2015-08-21 16:23:09 UTC
Version-Release number of selected component:
gtkhtml3-4.8.5-1.el7

Additional info:
reporter:       libreport-2.1.11

Comment 1 Jiri Koten 2015-08-21 16:27:58 UTC
Reproducer:

1) run gtkhtml-editor-test
2) Click Insert Image
3) Click Insert Link

Comment 2 Jiri Koten 2015-08-21 16:28:19 UTC
Created attachment 1065638 [details]
File: backtrace

Comment 3 Milan Crha 2015-08-26 11:40:44 UTC
Created attachment 1067229 [details]
patch to fix the crash

Comment 4 Milan Crha 2015-08-26 11:44:52 UTC
The problem was that there was no type-checking, thus even the cursor was at an image object the code cast the structure to a text object, thus it was reading data which was not there. I added type-checking and fixed a cursor positioning, thus the changes in the URL description don't delete the image object.

Comment 7 errata-xmlrpc 2015-11-19 07:59:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2226.html


Note You need to log in before you can comment on or make changes to this bug.