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 262607 - gnopernicus tries to access the expired a11y object of gtkhtml
gnopernicus tries to access the expired a11y object of gtkhtml
Status: RESOLVED INCOMPLETE
Product: GtkHtml
Classification: Other
Component: API
unspecified
Other All
: Normal enhancement
: ---
Assigned To: mengjie yu
Evolution QA team
Depends on:
Blocks: 244862 271192
 
 
Reported: 2004-08-06 06:10 UTC by Eric Zhao
Modified: 2006-09-15 21:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Eric Zhao 2004-08-06 06:10:54 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. start evolution with accessibility enabled.
2. start gnopernicus
3. Compose a HMTL message(with HTML format turned on)
4. Input some words, and make the font to +1.

Actual Results:
the following messages are outputted in console:
** (lt-test_editor:6870): CRITICAL **: file text.c: line 335
(html_a11y_text_get_caret_offset): assertion `p && html_object_is_text(p)'
failed

** (lt-test_editor:6870): CRITICAL **: file text.c: line 527
(html_a11y_text_get_character_count): assertion `to' failed

** (lt-test_editor:6870): CRITICAL **: file text.c: line 422
(html_a11y_text_get_text_at_offset): assertion `to' failed


Expected Results:
When a html object is destroyed, gnopernicus should be notified to destroy
the corresponding a11y object and not to access it any more.

How often does this happen? 
always.

Additional Information:
Comment 1 Kaushal Kumar 2005-09-23 06:56:44 UTC
Mengjie: Any news on this one.
Comment 2 André Klapper 2006-06-20 22:06:28 UTC
eric zhao, mengjie yu: any news on this? is this still valid?
Comment 3 André Klapper 2006-09-15 21:20:36 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!