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 330970 - gok makes the mouse stop working
gok makes the mouse stop working
Status: RESOLVED FIXED
Product: gok
Classification: Deprecated
Component: general
1.0.x
Other Linux
: Normal major
: ---
Assigned To: David Bolter
David Bolter
Depends on:
Blocks:
 
 
Reported: 2006-02-13 09:51 UTC by Kjartan Maraas
Modified: 2006-02-15 09:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch to fix the warning (1.42 KB, patch)
2006-02-14 20:48 UTC, Kjartan Maraas
accepted-commit_now Details | Review

Description Kjartan Maraas 2006-02-13 09:51:17 UTC
I enabled a11y on my fedora rawhide setup and set gok to start on login. When I logged out and back in the mouse stopped working totally. This only happens when gok is started and is confusing to say the least.
Comment 1 Kjartan Maraas 2006-02-14 14:01:47 UTC
Oh, it was the screenreader that was active it seems. Does that explain anything? Moving to gnopernicus.
Comment 2 Kjartan Maraas 2006-02-14 14:04:07 UTC
Rah. I'm on crack. enabling a11y and starting gok proves my first hunch to be right.
Comment 3 Kjartan Maraas 2006-02-14 20:46:52 UTC
This is possibly related to G_DEBUG=fatal_warnings when running gok I see this warning:

[kmaraas@localhost eog]$ gok
Bonobo accessibility support initialized
GTK Accessibility Module initialized
/dev/js0: Ingen slik fil eller filkatalog
3 event types available
login mode = false
Word prediction dictionary contains a total of 3000 words

Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed

Running gok in gdb with the --sync option gives me this backtrace:

[kmaraas@localhost eog]$ gdb gok
GNU gdb Red Hat Linux (6.3.0.0-1.98.2rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) r --sync
Starting program: /usr/bin/gok --sync
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xaf5000
[Thread debugging using libthread_db enabled]
[New Thread -1209002320 (LWP 18866)]
Bonobo accessibility support initialized
GTK Accessibility Module initialized
/dev/js0: Ingen slik fil eller filkatalog
3 event types available
login mode = false
Word prediction dictionary contains a total of 3000 words

Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
aborting...

Program received signal SIGTRAP, Trace/breakpoint trap.

Thread NaN (LWP 18866)

  • #0 IA__g_logv
    at gmessages.c line 503
  • #1 IA__g_log
    at gmessages.c line 517
  • #2 IA__g_return_if_fail_warning
  • #3 IA__gtk_widget_destroy
    at gtkwidget.c line 1993
  • #4 gok_main_close_warning
    at main.c line 2903
  • #5 gok_input_detach_corepointer
    at gok-input.c line 199
  • #6 gok_main_warn
    at main.c line 2956
  • #7 gok_main_warn_corepointer
    at main.c line 2933
  • #8 gok_main_open
    at main.c line 801
  • #9 main
    at main.c line 450

which pointed me to gok_main_close_warning()

Attaching a patch to check for a NULL _corepointer_warning before calling gtk_widget_destroy() on it.

That fixed the problem for me.

I have problems with my mouse though. After running and quitting gok the mouse no longer works. running xsetpointer Synaptics gets it back though.
Comment 4 Kjartan Maraas 2006-02-14 20:48:26 UTC
Created attachment 59364 [details] [review]
patch to fix the warning
Comment 5 David Bolter 2006-02-14 21:02:19 UTC
Comment on attachment 59364 [details] [review]
patch to fix the warning

Thanks!
Comment 6 Kjartan Maraas 2006-02-15 09:12:47 UTC
Commited.