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 504042 - Type of "accesible-value" property of an AtkObject doesn't conform to AtkValue interface
Type of "accesible-value" property of an AtkObject doesn't conform to AtkValu...
Product: atk
Classification: Platform
Component: atk
Other Linux
: Low normal
: ---
Assigned To: ATK maintainer(s)
ATK maintainer(s)
Depends on:
Reported: 2007-12-17 13:50 UTC by Andrey Tsyvarev
Modified: 2021-06-10 11:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Andrey Tsyvarev 2007-12-17 13:50:26 UTC
The "accessible-value" property of AtkObject has type gdouble. The get/set functions provided for this purpose use the functions from AtkValue interface which should be implemented by the descendant of AtkObject.

However AtkValue works with an arbitrary GValue which may contain data of any type, not only gdouble. For example it can be gint or something else.

This can lead to errors in setting/reading the value of the property. E.g. one cannot read the value of the property "accessible_value", if atk_value_get_current_value returns GValue of type, which differs from G_TYPE_DOUBLE.

The detailed bug description can be found at:
Comment 1 André Klapper 2011-06-23 22:07:00 UTC
[Mass-reassigning open atk bug reports for better trackability as requested in .
If you have watched the previous assignee of this bug report as a workaround for actually getting notified of changes in atk bugs, you yourself will now have to add atk-maint@gnome.bugs to your watchlist at the bottom of to keep watching atk bug reports in GNOME Bugzilla.
Sorry for the noise: Feel free to filter for this comment in order to mass-delete the triggered bugmail.]
Comment 2 André Klapper 2021-06-10 11:28:04 UTC
GNOME is going to shut down in favor of
As part of that, we are mass-closing older open tickets in
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of atk, then please follow
and create a ticket at

Thank you for your understanding and your help.