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 248664 - Program crash when using at-poke to edit text in e-text
Program crash when using at-poke to edit text in e-text
Status: RESOLVED FIXED
Product: GAL
Classification: Deprecated
Component: EText
trunk
Other All
: Normal minor
: ---
Assigned To: tim.wo
Evolution QA team
Depends on:
Blocks: 244862
 
 
Reported: 2003-09-20 08:41 UTC by tim.wo
Modified: 2004-09-29 20:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description tim.wo 2003-09-20 08:41:05 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
Program crash when using at-poke to edit(copy/cut/delete/paste) text in e-text

Steps to reproduce the problem:
1. export GNOME_ACCESSIBILITY=1
2. launch a program using e-text(e.g. test-text in "tests" dir of gal)
3. use at-poke to poke the e-text widget.
4. select nothing in e-text and then press "delete" in at-poke

Actual Results:
program crash (in my system I have to restart X)

Expected Results:
don't crash

How often does this happen? 
always

Additional Information:
Comment 1 tim.wo 2003-09-20 08:53:47 UTC 
This bug is caused by incomplete implementation of gal-a11y-e-text.
When press "delete" (or "cut","copy",etc) in at-poke, at-poke will
invoke the function "et_delete_text" in
gal/a11y/e-text/gal-a11y-e-text.c. The function needs 2 params
(start_pos and end_pos) which give the range of the text being delete.
But at-poke will pass some invalid values into the function. This is
bacause at-poke will get the selection range as the input params of
et_delete_text, and the selection range of e-text is retrieved by the
function "et_get_selection" which hasn't been complete yet.
Anyway, in "et_delete_text" some checking code is needed to ensure the
range of text being delete is valid.
Comment 2 tim.wo 2003-10-18 13:59:23 UTC 
after applying new patch (see bug 247034) bug resolved