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 125064 - gdm2/gok problems
gdm2/gok problems
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
unspecified
Other All
: Urgent critical
: ---
Assigned To: GDM maintainers
GDM maintainers
AP1
Depends on:
Blocks:
 
 
Reported: 2003-10-20 20:30 UTC by Brian Cameron
Modified: 2004-01-06 19:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description Brian Cameron 2003-10-20 20:30:07 UTC
If you launch the XDMCP Chooser from the login screen, and then use
the gesture listener framework to launch gok (via the control-k gesture),
then hit the Cancel button, then the Chooser program exits, but the GOK 
program never exits.  Making the computer unusable without restarting gdm.

Also, I notice that since gok uses gconf, that the gdm gconf process is
still running after the user has logged in.  It would be nice if gdm killed
any such processes created by the gesture listeners before logging in the
user.  This might need to be a bit clever since you might have a situation
where a user is logging in on the console and a second user is logging in
remotely.  The gconf process probably shouldn't be killed until the last
gdm GUI program exits.

Note, to turn on the gesture listener framework, the AddGtkModules should
be set to "true" and GtkModulesList needs to be uncommented (note that you
may have to change the value of GtkModulesList to the include the full path
of the GTK_MODULE libraries if the modules aren't installed to the same
location as GTK+'s modules - if you used a different --prefix when
configuring gdm2 vs gtk+, in other words).
Comment 1 George Lebl 2004-01-06 19:49:26 UTC
First and last problem now fixed in CVS.  The first problem was bad
reading of the output from the chooser which uses stdout, but the
accessibility modules thingies mess that up.  The last problem I fixed
a few days ago.  There is an accessibility setting in the config that
puts the entire paths in, and the default config file has the whole
paths as well.