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 110276 - GOK segfaults when trying to access invalid action
GOK segfaults when trying to access invalid action
Status: RESOLVED FIXED
Product: gok
Classification: Deprecated
Component: general
unspecified
Other All
: Urgent critical
: ---
Assigned To: bill.haneman
bill.haneman
Depends on: 88033
Blocks:
 
 
Reported: 2003-04-08 16:20 UTC by bill.haneman
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description bill.haneman 2003-04-08 16:20:32 UTC 
GOK segfaults when it attempts to access a UI element, menu, or toolbar
that is no longer valid (for instance, when the application presenting it
has quite and GOK is still displaying the old info).
Comment 1 bill.haneman 2003-04-08 16:21:53 UTC 
to reproduce:

start GOK and 2 or 3 GNOME apps.  cycle though windows until GOK gets
confused.

Kill the app whose UI is being shown by GOK, then
activate the 'dead' UI element via dwell mode.  SEGV.
Comment 2 David Bolter 2003-04-09 14:10:23 UTC 
One can build gok with the --enable-logging-normal and the
--enable-logging-exceptional flags to produce possibly useful output 
If you happen to capture this output during a segv session, please
attach to this bug.
Comment 3 bill.haneman 2003-04-09 14:26:37 UTC 
sure thing David, I'll try to get log output for this soon.
Comment 4 David Bolter 2003-05-14 15:55:57 UTC 
Bill, I believe my commits today should rectify this.  I'll leave this
bug open for a while to give you time to check.
Comment 5 bill.haneman 2003-05-31 12:37:41 UTC 
well I think modulo the 88033 problem with at-spi's weird
activate/deactivate ordering, we've gotten rid of the triggering
condition.  However, bearing in mind that weird stuff does happen, we
need to find a way to robustly handle the error condition itself.

Will investigate post-GUADEC.
Comment 6 bill.haneman 2003-06-13 12:33:33 UTC 
*** Bug 114872 has been marked as a duplicate of this bug. ***
Comment 7 bill.haneman 2003-06-13 13:21:35 UTC 
This turns out to be caused by a bug in AT-SPI (at least, in most
scenarios - there may be isolated cases where other bugs are still
causing problems with state UI components).

Fix is in CVS for at-spi (thanks to Michael Meeks).